Printable View
[QUOTE=VinnieKramer;7384193]And occasionally still have the 502 error.[/QUOTE]You need to type [URL]HTTP://usasexguide.nl/forum.[/URL].
Your browser usually makes it HTTPS: Usasexguide does not support the SECURE protocol so the "S" in httpS: gives the 502 error.
Include http when typing in address bar.
[URL]http://www.usasexguide.nl[/URL]
Note, it is NOT https.
[QUOTE=VinnieKramer;7384193]And occasionally still have the 502 error.[/QUOTE]
I've tried everything that I've read on here, plus some other strategies including shutting off all the security protocols on my Edge and Chrome browsers, 2 different VPNs plus Cloudflare Warp, clearing everything, changing my DNS to 1. 1. 1. 1 & 8. 8. 8. 8, and I'm still getting 502 on my Edge, Chrome, Firefox, and Duck, Duck, Go.
It works fine on the same wifi and internet gateway on my Samsung Phone Browser, though it doesn't work on phone's chrome brower.
My tech skills are there, but a bit dated. Any of you young guns got any suggestions. Reading this on my phone is a pain in the ass.
[QUOTE=SnoMan;7384356]Include http when typing in address bar.
[URL]http://www.usasexguide.nl[/URL]
Note, it is NOT https.[/QUOTE]
[QUOTE=Cincy;7390240]I've tried everything that I've read on here, plus some other strategies including shutting off all the security protocols on my Edge and Chrome browsers, 2 different VPNs plus Cloudflare Warp, clearing everything, changing my DNS to 1. 1. 1. 1 & 8. 8. 8. 8, and I'm still getting 502 on my Edge, Chrome, Firefox, and Duck, Duck, Go.
It works fine on the same wifi and internet gateway on my Samsung Phone Browser, though it doesn't work on phone's chrome brower.
My tech skills are there, but a bit dated. Any of you young guns got any suggestions. Reading this on my phone is a pain in the ass.[/QUOTE]I had luck downloading the Firefox browser, no problems at all.
I have been fine ever since I started typing the complete URL with http:
I do have to use a VPN. I can't even ping the site with my VPN off. My IP must be on a blacklist or something.
Sno.
[QUOTE=Cincy;7390240]I've tried everything that I've read on here, plus some other strategies including shutting off all the security protocols on my Edge and Chrome browsers, 2 different VPNs plus Cloudflare Warp, clearing everything, changing my DNS to 1. 1. 1. 1 & 8. 8. 8. 8, and I'm still getting 502 on my Edge, Chrome, Firefox, and Duck, Duck, Go.
It works fine on the same wifi and internet gateway on my Samsung Phone Browser, though it doesn't work on phone's chrome brower.
My tech skills are there, but a bit dated. Any of you young guns got any suggestions. Reading this on my phone is a pain in the ass.[/QUOTE]
[QUOTE=SnoMan;7390435]I do have to use a VPN. I can't even ping the site with my VPN off. My IP must be on a blacklist or something.[/QUOTE]I believe the site has been blacklisted and removed from the routing table for some ISPs. There was some chatter about this being the case for Verizon wireless a little while back, not sure if that's still the case. VPNs are your friend, for now anyway.
I have noticed that the Duck Duck Go browser on my phone no longer displays the site correctly. The Brave browser seems to do better, but also isn't perfect. I believe at least some of the display issues that people are seeing are technical issues with the site.
I'm personally not thrilled that HTTPS is not enabled. That means all traffic is being sent to and from the server unencrypted, which means anyone can intercept and watch your traffic to the site.
[QUOTE=TheDudeAbides3;7390767]I believe the site has been blacklisted and removed from the routing table for some ISPs. There was some chatter about this being the case for Verizon wireless a little while back, not sure if that's still the case. VPNs are your friend, for now anyway.
I have noticed that the Duck Duck Go browser on my phone no longer displays the site correctly. The Brave browser seems to do better, but also isn't perfect. I believe at least some of the display issues that people are seeing are technical issues with the site.
I'm personally not thrilled that HTTPS is not enabled. That means all traffic is being sent to and from the server unencrypted, which means anyone can intercept and watch your traffic to the site.[/QUOTE]See my post 7999 below. It is an HTTPS issue that is easily worked around.