Forums

My website is not secured

i'm using the free account option and after deploying, I get "not secured" at the address bar next to the url. Is that supposed to be normal?

that sounds like it's because you have http content inside of a https website (eg: say one of your pictures is loaded over http)

How is one to go about in fixing it? I mean, I have the same problem as a PAID member and I'm creating a social media website, of all web addresses to say "not secure"

i forced ssl and now it has a red "not secure"! Help me please!

Hi there, your issue is slightly different from the OP. You need an SSL certificate. More info here: https://help.pythonanywhere.com/pages/SSLOwnDomains/

I am having the same problem. I am using a free account and i don't think I am using any other http content on the website. What else could be the problem?

If you go to http://bharathanmudaliar.pythonanywhere.com/ it will show up as insecure. https://bharathanmudaliar.pythonanywhere.com/ it will show up as secure.

If you want to always redirect to https, you can do it yourself in your code, or you can use our webapp config "Force HTTPS" option.

My account is a free account. I tried to 'Force HTTPS' on my web configuration page, but it is not getting enabled. The slider remains 'Disabled'. What would be the problem?

When you clicked on the slider did it change from disabled to enabled? (that is what it should do- I wonder if perhaps you weren't clicking on the right side of the slider)

It worked!! Thanks, @conrad!!! All the time I was clicking on the blank area, assuming the slider will move to the clicked side.

Mine won't even let me log in and brings up errors about a not secure notification. I did move the slider so it says enabled. What else could I be missing? Thanks.

Did you reload your web app after making the change? Are you accessing the site using https?

It worked for me! I just enabled the "force https" slider and now, after reloading the website on the web app page, it shows as a secure website.

Yes, that will work well! The only time that "Force HTTPS" is a bad idea is if you've just created a website on a custom domain (that is, one that doesn't end with .pythonanywhere.com) and you haven't set up an HTTPS certificate.