Page 1 of 1

Getting a weird warning message

Posted: Mon Dec 10, 2012 1:11 am
by Thomaston
I've been getting the following message a lot lately when navigating to the forum:

Image

Additionally, once I get here I have to put my log-in info back in.
Just wondering if anyone else is getting this, and what's causing it.

Re: Getting a weird warning message

Posted: Mon Dec 10, 2012 2:26 am
by MTGuru
Hmmm, everything is fine for me with Firefox and IE.

Maybe your browser is trying a reverse DNS lookup on our IP and getting the server name (midas.dreamhost.com)? I don't think we have multiple PTR records, including one for forums.chiffandfipple.com.

Or are you pointing to the old chiffboard.mati.ca which redirects here?

Re: Getting a weird warning message

Posted: Mon Dec 10, 2012 3:08 am
by Thomaston
Could be. I'll try updating my bookmark and see if that fixes it.

Re: Getting a weird warning message

Posted: Mon Dec 10, 2012 4:19 am
by Tor
MTGuru wrote: Or are you pointing to the old chiffboard.mati.ca which redirects here?
The forum link on http://www.chiffandfipple.com/ (i.e. the front page) still points to chiffboard.mati.ca

-Tor

Re: Getting a weird warning message

Posted: Mon Dec 10, 2012 4:59 am
by MTGuru
Tor wrote:The forum link on http://www.chiffandfipple.com/ (i.e. the front page) still points to chiffboard.mati.ca
Yes, which should be fine, normally. My personal browser link points there, too. That's how lazy I am. :)

Re: Getting a weird warning message

Posted: Mon Dec 10, 2012 7:19 am
by Thomaston
The bookmark wasn't the issue. Maybe it's my ipod. I got the same message when trying to visit thesession.org.

Re: Getting a weird warning message

Posted: Mon Dec 10, 2012 8:16 am
by MTGuru
Thomaston wrote:The bookmark wasn't the issue. Maybe it's my ipod. I got the same message when trying to visit thesession.org.
I just checked, and I see that www.thesession.org has no reverse DNS record either. Not that that's the definite explanation.

Re: Getting a weird warning message

Posted: Mon Dec 10, 2012 8:48 am
by kkrell
Possibly a security/certificate issue. Many sites do not properly identify themselves as the site you're seeking, or are using an invalid or expired certificate. Can even be the difference between whether the URL uses www. in front of it or not. You may have the ability to relax any security settings in the Chrome browser.