View Full Version : Is the site blocked now in the us?
I had to get on my vpn machine to realize it was still up at all.
Craven Morehed
09-01-25, 20:34
Was wondering the same myself, I started using the Tor Browser to access.
But right now I can access it from firefox no problem, in the morning is when I have the most trouble.
I get 502 Bad gateway errors.
Billy Thornton
09-01-25, 20:54
I had that error for a while. Site had been working but I couldn't access it in Google Chrome because it was changing the http to https. I changed safety configuration. Now I have no issues because The address stays like http: etc. I can't access it in incognito mode because the change doesn't apply in that setting.
Was wondering the same myself, I started using the Tor Browser to access.
But right now I can access it from firefox no problem, in the morning is when I have the most trouble.
I get 502 Bad gateway errors.
BoltonChaser
09-01-25, 23:03
...I couldn't access it in Google Chrome because it was changing the http to https. I changed safety configuration. Now I have no issues because The address stays like http: ...This is correct. I get a "502 Bad Gateway" error when page loads via HTTPS. Loads fine with HTTP. Just type the full URL as http://www.usasexguide.nl and it'll load.
The site owner will need to fix, a quick check in the server logs will show the cause, it's probably a mismatch between a SSL server proxied to one with non-SSL. Nothing you can do fix other than avoid SSL, by just typing HTTP: Until fixed. That solution should work in any browser, Incognito mode or not.
This is correct. I get a "502 Bad Gateway" error when page loads via HTTPS. Loads fine with HTTP. Just type the full URL as http://www.usasexguide.nl and it'll load.
The site owner will need to fix, a quick check in the server logs will show the cause, it's probably a mismatch between a SSL server proxied to one with non-SSL. Nothing you can do fix other than avoid SSL, by just typing HTTP: Until fixed. That solution should work in any browser, Incognito mode or not.Thabks guys that works. Should have thought about that.
This is correct. I get a "502 Bad Gateway" error when page loads via HTTPS. Loads fine with HTTP. Just type the full URL as http://www.usasexguide.nl and it'll load.
The site owner will need to fix, a quick check in the server logs will show the cause, it's probably a mismatch between a SSL server proxied to one with non-SSL. Nothing you can do fix other than avoid SSL, by just typing HTTP: Until fixed. That solution should work in any browser, Incognito mode or not.This stopped working for me unfortunately.
This stopped working for me unfortunately.I have had zero problems using 3 different devices. My tablet and phone are Samsung and on my PC I use Microsoft Edge. My laptop is also Microsoft edge but haven't logged on with that in months.
BoltonChaser
09-06-25, 12:57
This stopped working for me unfortunately.When it fails, look at the full URL again. You might have to click the URL bar, some browsers hide the "http: www. " part because it's somewhat useless to show. If it has reverted to "HTTPS" just click and change back to "HTTP".
Your browser. Or a browser extension. Might be automatically redirecting to the HTTPS version. That's usually a setting where it prefers "secure content". While you can overwrite / disable that setting in your browser, it may add an entry for this website's URL. Which I'd generally guide against doing, because last thing anyone needs is a permanent log in our browsers of visiting this site.
If anyone wants to disable enforcing HTTPS, thus allowing you to visit HTTP (without the S) urls, search "YourBrowserName + disable secure content". Or check if you use a browser extension like HTTPS Everywhere (https://www.eff.org/https-everywhere).
Craven Morehed
09-07-25, 11:08
Your browser. Or a browser extension. Might be automatically redirecting to the HTTPS version. That's usually a setting where it prefers "secure content". While you can overwrite / disable that setting in your browser, it may add an entry for this website's URL. Which I'd generally guide against doing, because last thing anyone needs is a permanent log in our browsers of visiting this site.
.This what keeps happening to me using Firefox, just remove the "s" and it works fine until a close the browser.
I also use the Firefox private browser and that seems to help.
When it fails, look at the full URL again. You might have to click the URL bar, some browsers hide the "http: www. " part because it's somewhat useless to show. If it has reverted to "HTTPS" just click and change back to "HTTP".
Your browser. Or a browser extension. Might be automatically redirecting to the HTTPS version. That's usually a setting where it prefers "secure content". While you can overwrite / disable that setting in your browser, it may add an entry for this website's URL. Which I'd generally guide against doing, because last thing anyone needs is a permanent log in our browsers of visiting this site.
If anyone wants to disable enforcing HTTPS, thus allowing you to visit HTTP (without the S) urls, search "YourBrowserName + disable secure content". Or check if you use a browser extension like HTTPS Everywhere (https://www.eff.org/https-everywhere).Actually seems to be a browser issue on mobile. Automatically puts the s back in. Had to use a diff browser.
When it fails, look at the full URL again. You might have to click the URL bar, some browsers hide the "http: www. " part because it's somewhat useless to show. If it has reverted to "HTTPS" just click and change back to "HTTP".
Your browser. Or a browser extension. Might be automatically redirecting to the HTTPS version. That's usually a setting where it prefers "secure content". While you can overwrite / disable that setting in your browser, it may add an entry for this website's URL. Which I'd generally guide against doing, because last thing anyone needs is a permanent log in our browsers of visiting this site.
If anyone wants to disable enforcing HTTPS, thus allowing you to visit HTTP (without the S) urls, search "YourBrowserName + disable secure content". Or check if you use a browser extension like HTTPS Everywhere (https://www.eff.org/https-everywhere).Yep, had to jump through a few hoops and got MS Edge to finally let me in (not incognito mode though), although not sure if I can reply to messages using Edge. Using Firefox right now to write this.
Powered by vBulletin® Version 4.1.4 Copyright © 2026 vBulletin Solutions, Inc. All rights reserved.