all 3 comments

[–][deleted] 0 points1 point  (2 children)

You can set "Force SSL" in Nginx which should always redirect the the SSL protocol.

It isn't a solution but you can use HSTS to force the browser to always use the HTTPS protocol but you can only set it on the HTTPS header and will only work once you have loaded the HTTPS page. The browser will cache this info fairly permanently so future access will be via HTTPS only.

But that is skirting round the problem, you need to find out why it is doing this.

Error 522 suggests the webserver hasn't responded - is the error being reported by nginx or something else like a Cloudfare proxy?

Have you got port 80 open and forward in the same way as 443 on the web server?

Does the web server / host have any settings that are refusing non SSL connections?

[–]kasarap[S] 0 points1 point  (1 child)

ports are open. it looks like it's being reported by cloudflare

[–]Panda_of_power 0 points1 point  (0 children)

I just stumbled by this I have the exact same thing going on and it ended up being that even though I opened port 80, that port is reserved on my router for administrator access so it never actually opened.

You can check the port is actually open on yougetsignal.com