502 bad gateway

**Jack A Dogov** · 08-31-25 19:39

Originally Posted by JackADogov [View Original Post]

I'm using Firefox on a PC and I found a solution that works for me. Just update your bookmark for this site from www.usasexguide.nl to http://www.usasexguide.nl.

There's another way in. When I kept getting the bad gateway and before I figured out the http (s) thing, I would access the site by going to its sister site: http://internationalsexguide.nl/. There's a link to this site on there and it would let me in through that.

**Wabbitt9** · 08-30-25 16:25

Originally Posted by Ayasaki [View Original Post]

I had no issues using Firefox on my Windows PC, but after a discussion with a local, I went through some steps to trigger this problem for myself in Chrome (on Windows and Android). Ultimately, came to the conclusion a VPN worked for Chrome sometimes. However, I revisited one of the ideas I had searched earlier and there is a much simpler way of dealing with it on both Windows and Android Chrome (can't and won't test on IOS).

https://www.chromium.org/Home/chromi...ecure-origins/

Basically use this flag.

chrome://flags/#unsafely-treat-insecure-origin-as-secure

Relaunch browser after changing this and then directly enter http://www.usasexguide.nl . Without doing both of these steps, at least on my device, Chrome will add the http s part and even when you remove the 's', it will continue to re-add it again and again. Likely the reason my past attempts failed at making it work earlier.

And while I have no particular reason to check all browsers, I do have Edge so checked it there since it is also Chromium behind the scenes and the same process works (just use edge://flags/ instead).

That worked perfectly on both my phone and tablet (which is my usual way of browsing the site). Chrome on my PC actually listens when I type http and doesn't force add the 's'.

And I agree with the fellow who said that, once the SSL certificate issue is fixed, I'll be changing my password.

**RandyWanker** · 08-29-25 17:51

I'm using the latest updated w11 pro. I am gatewayed when using ExpressVPN. When I "disconnect" it, no 402 error.

**VanillaStick** · 08-29-25 17:34

Originally Posted by DaveSalem [View Original Post]

I have gotten the above error on my Android SAFARI browser for months and gave up trying because I generally have access to a PC with Mozilla Firefox, which has always worked.

I emailed admin2 that I could not connect and they responded "what error", and failed to respond to the BAD GATEWAY response.

I'm getting this on my PC, I have an older PC running win7 and can access it fine, I can reach it on my iPhone with google and safari. My current PC is win 11 pro. It doesn't seem to be an iSP issue I’m using my home internet for all these devices I’ve disabled the firewall settings also. Could it be a browser compatibility issues on a newer update?

**DaveSalem** · 08-29-25 11:22

Originally Posted by DarbyDarby2221 [View Original Post]

This worked for me, Thanks! Was using duckduckgo in the interim.

I have gotten the above error on my Android SAFARI browser for months and gave up trying because I generally have access to a PC with Mozilla Firefox, which has always worked.

I emailed admin2 that I could not connect and they responded "what error", and failed to respond to the BAD GATEWAY response.

**Ayasaki** · 08-28-25 13:41

Originally Posted by DarbyDarby2221 [View Original Post]

This worked for me, Thanks! Was using duckduckgo in the interim.

Glad it helped someone. Actually one of the biggest problems with this is the fact that if the solution is here. It requires someone to successfully make it through the errors at least once. And a lot of people are understandably asking their individual local boards.

But like if someone never got through in the first place, they won't see how to solve this. I'm thinking back to my own local boards, is it quiet now because there's no one interesting to post about, or is it quiet because the prominent posters don't know how to get back?

**DarbyDarby2221** · 08-28-25 07:50

This worked for me, Thanks! Was using duckduckgo in the interim.

Originally Posted by Ayasaki [View Original Post]

I had no issues using Firefox on my Windows PC, but after a discussion with a local, I went through some steps to trigger this problem for myself in Chrome (on Windows and Android). Ultimately, came to the conclusion a VPN worked for Chrome sometimes. However, I revisited one of the ideas I had searched earlier and there is a much simpler way of dealing with it on both Windows and Android Chrome (can't and won't test on IOS).

https://www.chromium.org/Home/chromi...ecure-origins/

Basically use this flag.

chrome://flags/#unsafely-treat-insecure-origin-as-secure

Relaunch browser after changing this and then directly enter http://www.usasexguide.nl . Without doing both of these steps, at least on my device, Chrome will add the http s part and even when you remove the 's', it will continue to re-add it again and again. Likely the reason my past attempts failed at making it work earlier.

And while I have no particular reason to check all browsers, I do have Edge so checked it there since it is also Chromium behind the scenes and the same process works (just use edge://flags/ instead).

**MikeOxHuge** · 08-27-25 21:26

I'm getting the error on all browsers on my phone and PC. Firefox is the only one I've been able to get on, after forcing it to not use https for this site, which is really not a good thing.

**Billy Thornton** · 08-27-25 08:16

Thank you. After not being able to access site for 2 weeks, I was able to use it today. I didn't make any changes but I'll keep these suggestions in my files.

Originally Posted by Ayasaki [View Original Post]

I had no issues using Firefox on my Windows PC, but after a discussion with a local, I went through some steps to trigger this problem for myself in Chrome (on Windows and Android). Ultimately, came to the conclusion a VPN worked for Chrome sometimes. However, I revisited one of the ideas I had searched earlier and there is a much simpler way of dealing with it on both Windows and Android Chrome (can't and won't test on IOS).

https://www.chromium.org/Home/chromi...ecure-origins/

Basically use this flag.

chrome://flags/#unsafely-treat-insecure-origin-as-secure

Relaunch browser after changing this and then directly enter http://www.usasexguide.nl . Without doing both of these steps, at least on my device, Chrome will add the http s part and even when you remove the 's', it will continue to re-add it again and again. Likely the reason my past attempts failed at making it work earlier.

And while I have no particular reason to check all browsers, I do have Edge so checked it there since it is also Chromium behind the scenes and the same process works (just use edge://flags/ instead).

**Ayasaki** · 08-27-25 03:42

I had no issues using Firefox on my Windows PC, but after a discussion with a local, I went through some steps to trigger this problem for myself in Chrome (on Windows and Android). Ultimately, came to the conclusion a VPN worked for Chrome sometimes. However, I revisited one of the ideas I had searched earlier and there is a much simpler way of dealing with it on both Windows and Android Chrome (can't and won't test on IOS).

https://www.chromium.org/Home/chromi...ecure-origins/

Basically use this flag.

chrome://flags/#unsafely-treat-insecure-origin-as-secure

Relaunch browser after changing this and then directly enter http://www.usasexguide.nl . Without doing both of these steps, at least on my device, Chrome will add the http s part and even when you remove the 's', it will continue to re-add it again and again. Likely the reason my past attempts failed at making it work earlier.

And while I have no particular reason to check all browsers, I do have Edge so checked it there since it is also Chromium behind the scenes and the same process works (just use edge://flags/ instead).

**WhiteSun777** · 08-25-25 17:15

Trying to dig into it some more (on the server side) The SSL checks are mostly good with the exception of TLS (server is supporting 1. 1) so I'm going to put a wild guess that most newer browsers are now flat out rejecting this due to its known security vulnerabilities

I'm going to guess if the server disable TLS 1. 1 (since it does support 1. 3) it should be good. Still not sure the root cause as it's been working OK till recently.

**Cartog** · 08-25-25 13:42

Originally Posted by WhiteSun777 [View Original Post]

For PC Firefox is the way to go for now, no settings to change, just manually remove the s for HTTP.

I'm not 100% sure on the iPhone but I suspect it's similar to iPad. Safari doesn't work for me but Chrome works fine without https.

And agreed, you wouldn't want to login without https. I'm definitely planning on changing my password when https is working again.

On my iPhone safari browser, I did find a work-around to get a good http connection to the site. I fully type the link as http://usasexguide.nl. However, if I use auto-fill when typing, make it a bookmark, or click on this link while on my iPhone, they all fail with Bad Gateway. All those attempts want to redirect to https. Not sure why the site does not seem to support https. Maybe has to do with all the DDOS attacks.

**WhiteSun777** · 08-25-25 13:36

Originally Posted by Lotsoffun201 [View Original Post]

I went to Google on my iPhone and it does the same thing. I can view the site, but can't log in to respond or click on any pictures as the login and password disappear. Chrome on my office computer (which I am on now) works fine for now.

Sadly I don't have a personal iPhone to mess with so I'm not sure what works. Since Safari and Chrome doesn't work, I would try other browsers e. G. Opera, FireFox, DuckDuckGo, etc. And see what sticks.

**Lotsoffun201** · 08-25-25 13:06

Originally Posted by WhiteSun777 [View Original Post]

I've seen this myself, I just refresh and try and try again. Some weird glitch.

I went to Google on my iPhone and it does the same thing. I can view the site, but can't log in to respond or click on any pictures as the login and password disappear. Chrome on my office computer (which I am on now) works fine for now.