10-21-2019, 12:33 AM
It seems like it's not safe to visit the archives anymore.
10-21-2019, 12:33 AM
It seems like it's not safe to visit the archives anymore.
10-21-2019, 12:53 AM
that's because of the server change I would guess, same as MFGG proper was for a while
10-21-2019, 10:13 AM
DONT VISIT THE ARCHIVES U WILL GET HACCED!!!!!;!;!;
Just ignore it. As long as you don't log in it should make no difference. I'll look into it regardless though.
10-21-2019, 06:38 PM
that error is like, the biggest lie that tech companies tell to the world lmfao
that error would mean something if you were not actually visiting the real mfgg and your internet connection were hacked or some malicious individual got a hold of our domain name. im not sure it means much outside of those circumstances; i even think your connection is still secured Vimimin Wrote:Hylian's day job, little did we know, was saying controversial things on the internet. Mors Wrote:you fool!!!! you fixed it wrong!!!! Bibby Team
10-21-2019, 07:34 PM
This is a low risk, but I'd caution against entering passwords on an unsecured site, especially if you're browsing from a public Wi-Fi hotspot. So wait until you get home from Starbucks or the airport before you log in to this forum that closed a decade ago!
Course clear! You got a card.
10-21-2019, 07:56 PM
So is it safe to log in? Are you guys going to fix it
10-21-2019, 09:59 PM
It's safe to log in to the IPB archives, at least if you're on a secured network (like your home network).
Other realms of MFGG (like this forum and the mainsite) use HTTPS, so it should be safe to log in to those from any standard Internet connection. Course clear! You got a card.
10-22-2019, 09:43 PM
Alright, so I'm trying to log in and it won't let me. I know for a fact my username and password are 100% correct. It asked for a username eeven though I already entered my username and password? So then I enter both again and it sends me back to the front page as a Guest.
10-27-2019, 03:29 AM
Something is auto-forwarding HTTP to HTTPS on that domain but I'm not quite sure what (SSL was supposedly left disabled for this domain).
I assigned it a certificate, but it's not going to change the error because every piece of content needs to also come from an HTTPS source, and domains like the archive were never meant to support that. |
|