I’m not sure if this is a long term issue or not, but I got some security warnings when pulling up the site for the first time - it looked like the certificate may have been bad, or it wasn’t using https like expected or something. I advanced through those warnings and am not seeing them any more… don’t know if that’s because things got fixed, or because something is being cached locally to make the browser ignore them.
It may be complaining about some assets not using https … I will get that fixed.
Here’s a screenshot showing it. Also note that before the browser catches the redirect for the first time, you get a TOO_MANY_REDIRECTS error. I suspect your Apache config is being fidgety.
I had that issue earlier when I first tried resetting the password. Changing from firefox to chrome helped me but that may just be because chrome tends to be less fidgety.
Yep, will get that fixed in a bit.
Actually, it’s both.
I can’t currently upload an image, but look at your browser console.
Yeah, I had to use imgur.
Anyway, this actually happens before any page content is loaded, so they are two totally separate issues. Here’s some curl output demonstrating what I’m talking about.
Openssl shows the issue quite clearly.
The mixed content errors are totally separate. If you look at your console, those all originate from www.chiefdelphi.com, which is covered under the certificate. It just uses the wrong protocol.
Using Chrome, I get an error trying to open the website, but not when I’m in incognito mode.
I just added an exception in Firefox so it ignores the warning.
Saw the same with Microsoft Edge on Windows 10. Total of 4 times since yesterday.
The hostname in the website’s security certificate differs from the website you are trying to visit.
Error Code: DLG_FLAGS_SEC_CERT_CN_INVALID
Chrome is fine.
I couldn’t do it the right way, due to the CD-Media rebuild taking forever, but I’ve got a temporary fix in place.
Let me know if you see any SSL errors anymore.
Ah, that temporary fix didn’t renew its Let’s Encrypt cert for some reason. It just needs to be permanently fixed. I’ll get that sometime this weekend.
This should be fixed (once your DNS updates).