Hello PythonAnywhere Support Team,
I am using a paid Hacker account and have a Flask web application running correctly on PythonAnywhere.
I have configured my custom domain , and I am accessing the application via www.tijaratfragrance.com. The DNS records are correctly pointed to PythonAnywhere, and the site is successfully handling non-secure HTTP requests (confirmed via access logs showing consistent 200 responses for pages and static assets).
However, when accessing the site over HTTPS, browsers show a security warning such as NET::ERR_CERT_COMMON_NAME_INVALID, and Chrome suggests proceeding in “safe mode”. The certificate being served appears to be the default *.pythonanywhere.com certificate rather than one issued for my custom domain.
According to PythonAnywhere’s documentation on setting up HTTPS for custom domains, once a custom domain is correctly pointed at PythonAnywhere and the site is reachable over HTTP, it should be possible to enable an auto-renewed Let’s Encrypt certificate from the Web → Security → HTTPS certificate section.
In my account, I do not see an option to attach or register my custom domain with the web app, nor do I see the ability to enable a Let’s Encrypt HTTPS certificate for the domain. Because of this, I am unable to complete the HTTPS setup myself.
Could you please:
Enable or attach the custom domain www.tijaratfragrance.com (and optionally tijaratfragrance.com) to my web application, and
Enable HTTPS by issuing an auto-renewed Let’s Encrypt certificate for the domain,
or let me know if there is any remaining verification step required from my side.
Everything on the DNS and application side appears to be correctly configured, and I believe only the custom-domain HTTPS binding remains to be completed.
