502 bad gateway

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

[QUOTE=Ayasaki;7381328]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).

[URL]https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins/[/URL]

Basically use this flag.

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

Relaunch browser after changing this and then directly enter [URL]http://www.usasexguide.nl[/URL] . Without doing both of these steps, at least on my device, Chrome will add the http [B]s[/B] 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).[/QUOTE]

[QUOTE=DarbyDarby2221;7382107]This worked for me, Thanks! Was using duckduckgo in the interim.[/QUOTE]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?

[QUOTE=DarbyDarby2221;7382107]This worked for me, Thanks! Was using duckduckgo in the interim.[/QUOTE]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 [B]admin2[/B] that I could not connect and they responded "what error", and failed to respond to the BAD GATEWAY response.

[QUOTE=DaveSalem;7382889]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 [B]admin2[/B] that I could not connect and they responded "what error", and failed to respond to the BAD GATEWAY response.[/QUOTE]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?

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

[QUOTE=Ayasaki;7381328]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).

[URL]https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins/[/URL]

Basically use this flag.

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

Relaunch browser after changing this and then directly enter [URL]http://www.usasexguide.nl[/URL] . Without doing both of these steps, at least on my device, Chrome will add the http [B]s[/B] 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).[/QUOTE]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.

[QUOTE=JackADogov;7378411]I'm using Firefox on a PC and I found a solution that works for me. Just update your bookmark for this site from [URL]www.usasexguide.nl[/URL] to [URL]http://www.usasexguide.nl[/URL].[/QUOTE]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: [URL]http://internationalsexguide.nl/.[/URL] There's a link to this site on there and it would let me in through that.

[QUOTE=DaveSalem;7382889]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 [B]admin2[/B] that I could not connect and they responded "what error", and failed to respond to the BAD GATEWAY response.[/QUOTE]Thank you for emailing admin2 about this. They MUST be aware of the issue, there's just no way they're NOT aware of this. Especially the amount of visitors that still can't get in. One look at their traffic report should tell them something's wrong.

Obviously there's no error if users aren't going via HTTPS.

As I suspect before, the issue is due to server accepting TLS 1. 1 which was released back in 2006 and almost all new browsers will no longer accept this due to security concerns. If they disable TLS 1. 1 on the server, it *should* fix the issue. Not 100% on this but that's what I would try first.

[QUOTE=JackADogov;7384264]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: [URL]http://internationalsexguide.nl/.[/URL] There's a link to this site on there and it would let me in through that.[/QUOTE]That didn't work for me.

I can now get in on chrome. Firefox works without any issues as well.

[QUOTE=WhiteSun777;7385367]Thank you for emailing admin2 about this. They MUST be aware of the issue, there's just no way they're NOT aware of this. Especially the amount of visitors that still can't get in. One look at their traffic report should tell them something's wrong.

Obviously there's no error if users aren't going via HTTPS.

As I suspect before, the issue is due to server accepting TLS 1. 1 which was released back in 2006 and almost all new browsers will no longer accept this due to security concerns. If they disable TLS 1. 1 on the server, it *should* fix the issue. Not 100% on this but that's what I would try first.[/QUOTE]Check out Phoenix / GeneralReports thread for more information, fascinating!

[QUOTE=Ayasaki;7381328]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).

[URL]https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins/[/URL]

Basically use this flag.

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

Relaunch browser after changing this and then directly enter [URL]http://www.usasexguide.nl[/URL] . Without doing both of these steps, at least on my device, Chrome will add the http [B]s[/B] 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).[/QUOTE]This worked, thanks.

Steps:

1. Enter the following into Chrome: chrome: flags /#unsafely-treat-insecure-origin-as-secure.

2. ENABLE and add [URL]http://www.usasexguide.nl[/URL].

3. Relaunch Chrome and it should work, note http and not https (may need to MANUALLY remove the S).

Thanks for all the help here. I haven't been on in weeks.

[QUOTE=Fuzion;7386056]This worked, thanks.

Steps:

1. Enter the following into Chrome: chrome: flags /#unsafely-treat-insecure-origin-as-secure.

2. ENABLE and add [URL]http://www.usasexguide.nl[/URL].

3. Relaunch Chrome and it should work, note http and not https (may need to MANUALLY remove the S).[/QUOTE]Chrome on my PC works just fine. It's my iphone on safari that doesn't work. Chrome on the iphone won't let me log in and DuckDuckGo doesn't work at all. I can manually enter http: but seems to revert to the secure site Bad Gateway after one or two clicks. I'm stumped.

Seems to be a pretty big deal to lose a lot of traffic to this issue, it took a while to figure out the workaround on my own as there doesn't seem to be any other communication channels for this site. I wonder who maintains the site and what the scope would be to fix the issue.