502 bad gateway

**Oc Amper** · 09-12-25 14:44

Originally Posted by Cartog [View Original Post]

I access this site mostly via my shitty Windows PC with the Edge browser, but on occasion I would like access it via my iPhone with the Safari browser. To access the site via Windows Edge, I need to use the HTTP not secure connection. I don't understand why that is, but I have lived with it. To keep Edge from automatically doing a redirect to HTTPS, I did recently need to turn off this Edge browser security setting: "Automatically switch to more secure connections with Automatic HTTPS". For security, I would prefer not to do this so If someone knows of a better solution let me know.

As for my iPhone safari browser, it looks like one of Apple's recent updates started triggering the 502 Bad Gateway issue. It now appears to me that Safari is redirecting all HTTP connections to HTTPs. Anyone know of a setting to turn this feature off on Safari?

Just curious also, does anyone access this site via an HTTPS connection and with what browser? Thanks.

Can't access the forum via HTTPS, even though the site seems to have a configured certificate. Seems like this all cropped up after the DDOS attacks as reported earlier here.

Hopefully, this gets resolved.

**Flight Time** · 09-11-25 22:24

Originally Posted by BadBird [View Original Post]

Oh, it WILL affect the bottom line. All the BS ads on this site. Traffic is WAY WAY WAY down, active logins are available and it is no where near what it was. Advertisers will not continue to pay like they have for a fraction of the viewers. Frankly, the fact they have not fixed it is very concerning. I have not been on ANY website in many years where HTTPS was not available. Questions motives, questions the validity of the website, questions if outside forces have taken over, especially when there this is NOT ANY OBVIOUS announcement to be found on the site. There should be some big bold link everywhere that takes you to an explanation and the current status, but there is not. Again, raising some big red flags.

I know they could give a shit care less, but I will not be returning until it is back to normal and I am sure I am not the only one.

BB out.

If economics is a motivator, it'd be fixed. That's all I'm saying. The Vbulletin version is massively out of date & support. It went out of support almost 14 years ago. Its going to be plagued by age related issues in both stability and security.

**Bad Bird** · 09-11-25 09:10

Originally Posted by FlightTime [View Original Post]

They've deleted posts after this one, so they've certainly been made aware. Lack of desire I guess, must not be affecting the bottom line.

Oh, it WILL affect the bottom line. All the BS ads on this site. Traffic is WAY WAY WAY down, active logins are available and it is no where near what it was. Advertisers will not continue to pay like they have for a fraction of the viewers. Frankly, the fact they have not fixed it is very concerning. I have not been on ANY website in many years where HTTPS was not available. Questions motives, questions the validity of the website, questions if outside forces have taken over, especially when there this is NOT ANY OBVIOUS announcement to be found on the site. There should be some big bold link everywhere that takes you to an explanation and the current status, but there is not. Again, raising some big red flags.

I know they could give a shit care less, but I will not be returning until it is back to normal and I am sure I am not the only one.

BB out.

**Flight Time** · 09-10-25 06:32

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.

They've deleted posts after this one, so they've certainly been made aware. Lack of desire I guess, must not be affecting the bottom line.

**Thunter** · 09-07-25 16:52

Originally Posted by Absence [View Original Post]

The lack of SSL / HTTPS is suspicious. I'm not a security expert but the lack of encryption means the whole site could be spoofed or cloned or the traffic could be exploited by a man in the middle attack.

I'm not worried about my personal stakes but this community is vulnerable. We are going to wake up one day and it's just going to be gone.

Then, what will we do?

I belive you are correct. There is no easy way to assure access and most browsers are forcing HTTPS use even if HTTP is entered. The vast majority of users don't have the ability to find work arounds and eventually even those workarounds will quit working. Postings on boards have really dropped off and just about every contact I had has vanished or when reached through another method can't view the site. Everything went HTTPS long ago and it's not difficult but seems to be lost here.

**Absence** · 09-07-25 01:00

The lack of SSL / HTTPS is suspicious. I'm not a security expert but the lack of encryption means the whole site could be spoofed or cloned or the traffic could be exploited by a man in the middle attack.

I'm not worried about my personal stakes but this community is vulnerable. We are going to wake up one day and it's just going to be gone.

Then, what will we do?

Originally Posted by SuroAwei [View Original Post]

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.

**GeniusCasanova** · 09-05-25 10:33

I could kiss you for your post. I haven't been able to get to the site on mobile for a few weeks now and was finally able to get in on a desktop to access this. Worked for me like a charm.

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).

.

**SuroAwei** · 09-05-25 03:01

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.

**Lotsoffun201** · 09-03-25 12:43

Originally Posted by Fuzion [View Original Post]

This worked, thanks.

Steps:

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

2. ENABLE and add http://www.usasexguide.nl.

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

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.

**Midnightpass** · 09-03-25 10:46

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

**Fuzion** · 09-03-25 09:23

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).

This worked, thanks.

Steps:

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

2. ENABLE and add http://www.usasexguide.nl.

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

**PDXFrosty** · 09-03-25 06:52

Originally Posted by WhiteSun777 [View Original Post]

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.

Check out Phoenix / GeneralReports thread for more information, fascinating!

**Warhawk** · 09-02-25 22:43

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

**Geneva Guy** · 09-02-25 13:16

Originally Posted by JackADogov [View Original Post]

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.

That didn't work for me.

**WhiteSun777** · 09-02-25 12:47

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.

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.