This is an error that has popped up for a handful of people trying to reach the forum. Obviously if you’re reading this you’re not affected (unless you changed networks and magically it works). For the life of me I cannot figure what caused this error, but I can confirm that the solution is not on the server end. I’ve refreshed the SSL certificates and done everything the command line will let me do on the VPS, and as far as I can tell it all checks out.
There is a solution that, as far as I know, has a 100% success rate:
Reset your router
That’s it. That has done the trick for at least 5 people that I’ve asked so far.
So if you’re having trouble accessing the forum at any point and you can reset your router, please do, and if you have friends who can’t reach the forum, spread the word.
This has all been very frustrating and I’d rather have a solution that I can push out myself, but as best I can figure some magic pixies took a wrong turn somewhere and resetting your router is the only way to wake up ‘em up and tell them to get back to work.
From the very little that I have read, it seems to be a client-side error, although, personally, I didn’t encounter it, neither on my desktop or my phone (I didn’t open it via WiFi from my phone just to be sure that I’m not connecting via my home router).
This article seems to indicate that it only occurs in Mozilla Firefox. For the affected users, have you asked what browser they are using?
I’ve run into this error on my router, on my iPhone and on both Firefox and Chrome on my PC, though I could still go on here with my 5G connection. Good to know it’s not just me that ran into this.
My router is a Technicolor XB7 from Xfinity. Would not be surprising if this ended up being a Comcast issue.
Most reports (and it’s less than 10 of them to be fair) say Firefox, but some have had it on any browser and device.
I am guessing when I still was messing around with some of the nginx stuff it messes things up in a cache on a small percentage of routers. Kinda hoping that means it only happens to people who visited in the early days before I fixed all that and it doesn’t happen to people who visit for the first time now.
I still haven’t been able to get Firefox to work (I tried unplugging and replugging in my router last night but still having issues) but I have been able to confirm to the best of my knowledge that it IS something in my router that is the problem. My phone when connected to my home wifi gives the same error but doesn’t when I switch to cellphone data, so, yeah. I’ll try resetting the router again sometime but it’s difficult because I need to wait till a time where it won’t disrupt somebody else using it.
EDIT: was just able to get it to connect by typing in “theunderscore.xyz” without anything extra. Something popped up warning me that the site might be risky but I clicked “connect anyway” and now it’s, fine? ok
This often is caused by a server sending http traffic over https, that is, not encrypting the response but sending it like the body of an http response. So while the server is configured to respond on port 443, it’s sending the same body as port 80. Make sure 443 is configured for SSL and not HTTP.
It can also happen if there’s a mismatch with port/https, ex. if some page is redirecting to a uri with https:// but contradictorily specifying :80
This actually makes sense. My router still seems to hate this website (I’ve tried resetting multiple times now) but I realized that the workaround I’ve been using (clearing the cache and manually typing in the URL) is causing it to use HTTP and not HTTPS, which causes a momentary freakout warning that this site is unsafe but still allowing me to click through and connect. Unfortunately it seems there is no way to permanently mark this website as safe, but it’s whatever.