[QUOTE=RickJohn;7387831]Anyone else getting 502 bad gateway when trying to access this website from a pc? I can access it fine with any iOS device. But can not log on from any pc with any browser. Even with computers at different locations.[/QUOTE]Had a buddy help me get around this. I had to switch to fire Fox and remove the S from https.
Basically it sounds like http lacks some serious security but this website doesn't really operate by 2025 security measures. Here an explanation from the robots.
1. Chrome is pushing HTTPS much harder.
Chrome has been steadily deprecating plain HTTP for years.
When you try to load an http: site, Chrome may attempt an "HTTPS upgrade" in the background (using things like HTTPS-First Mode, HSTS preload lists, or automatic HTTPS rewriting).
If the server doesn't support HTTPS properly, this can result in 502 Bad Gateway or similar errors in Chrome.
2. Firefox is more tolerant by default.
Firefox still allows http: connections in a straightforward way unless you manually enable HTTPS-Only Mode.
That's why it loads sites over HTTP without forcing the upgrade, so you don't get the same error.
3. Why a 502 Bad Gateway specifically?
A 502 usually means the browser's request went through a proxy / gateway (like Cloudflare, Nginx, or even Chrome's own upgrade handler) and failed.
In this case:
Chrome tries HTTPS → the site doesn't respond correctly → the gateway fails → Chrome shows 502.
Firefox just sticks with plain HTTP → the site loads (though insecure).
4. Things that can cause this in Chrome.
HTTPS-First Mode enabled in Chrome flags (sometimes auto-enabled in new builds).
HSTS (HTTP Strict Transport Security) rules cached for that domain.
Extensions that try to force HTTPS.
The site itself misconfigured (proxy / load balancer only answers cleanly on HTTP, not HTTPS).
✅ Fix / Workarounds:
1. In Chrome, check:
Settings → Privacy and Security → Security → toggle Always use secure connections.
2. Try clearing HSTS entries for that domain:
Go to chrome: net-internals /#hsts, search the domain, and delete it.
3. Test with an incognito window or fresh Chrome profile (rules may be cached).
4. If you control the site → add a valid TLS / SSL certificate so it works with HTTPS (the long-term solution).
