Forums

Newer information below:

According to the following: " Go to the "Web" tab, and click on the pencil icon next to the web app name. Change it from conrad.pythonanywhere.com to www.conradsdomain.com. " then the CNAME entry from the domain registration platform should look like below?

TYPE NAME VALUE

CNAME www.conradsdomain.com conrad.pythonanywhere.com

Thus, when a request is sent to www.conradsdomain.com, the DNS service would automatically redirect the requet to conrad.pythonanywhere.com. Then, users would see the www.conradsdomain.com address at their browser? or conrad.pythonanywhere.com ? Sound like the latter. But we really want the user to see www.conradsdomain.com URL.

Am I off? I don't know much about networking.

Original post below: I've read the following help page, https://help.pythonanywhere.com/pages/HTTPSSetup

Currently for my stuff on PA, it reads:

" Security: An HTTPS certificate is needed so that people can access your site securely. We automatically provide a certificate for {username}.pythonanywhere.com.

HTTPS certificate:Automatically provided for this hostname You need to Reload your web app to activate any changes made below. "

Question, does that cover a subset of it? for instance, {app2-username}.pythonanywhere.com ? Am I ready to go for https after reloading or anything else more involved?

Thanks.

Regarding the CNAME: no, it will be different and it's used to point to PythonAnywhere in a way that is not dependend on the IP address of our servers which are not fixed -- when a request comes to PythonAnywhere for a particular web app, our system delegates it to the proper server where your app is hosted on. If you change to a custom domain, the default domain will be no longer available. If you want an app to be available on both (custom and default domain), you'd need 2 web apps (ideally one redirecting to another).

SSL: all pythonanywhere.com subdomains have SSL certificate by default. The only change you can make to the web app setup is to force HTTPS.

Here's the screenshot that my domain registration company helped to create 2 Address Records and 1 CNAME for my_new_domain.

Here's the screenshot at PA after I renamed "myAccount-app2.pythonanywhere.com" to "www.mynewdomain.net":

What's wrong and how to fix it/them? Thanks.

I don't see any web apps on custom domains currently on your account, so it's hard to debug it -- did you revert back to defaoult PythonAnywhere subdomains or do you have multiple accounts?

Yes, I reverted back to {myapp2-myAccount}.pythonanywhere.com.

Question, based on the screenshot, is the 2 Address Records and 1 CNAME record setup correct from my domain registration side? I told the support {mydomin.net} needs to be redirected to pythonanywhere.com domain. Or do we need to add another CNAME record at "my_domain.net" registration site with the following content:

TYPE NAME VALUE

CNAME www.{mydomain.net} {myapp2-myAccount}.pythonanywhere.com ?

If such new CNAME record is needed, then, it would take about 24 hours for it to take effect.

You guys (assume in UK) are 5 hours ahead of us (US eastern time zone), I'd prefer to do the domain setup with PA during off peak hours and you folks are also available, what time frame would you suggest?

Thanks.

The correct CNAME should have "Name" www and "Value" webapp-<some number>.pythonanywhere.com

Got it. Should I wait for at least 20 hours after the new/edited CNAME record takes effect and then go to PA to rename webapp-<some number>.pythonanywhere.com to my_new_domain.net ?

Thanks.

No, you don't need to wait.

I now know where the problem is.

(1) The process flow should be doing the app "rename" at PA first and then

(2) Go to the domain registration site, to set up the CNAME because the webapp-<some number>.pythonanywhere.com was automatically generated by PA, and PA DNS setup uses this one, NOT for anything else. And then, put this FQDN at the domain registration site.

Man, I wish you folks would have straightened up the help page with a step-by-step guide vs. the current confusing one.

Working. Thank you.

Thanks for letting us know!