Tweet Security Certificate

I'm now getting warnings whenever I try to log in to NitrateVille, that the site is not secure and login information could be stolen.

When I go ahead and log in anyway, it takes longer to move into the home page from the login page. We're not talking minutes here, but it is a noticeable pause.

Jim

[Mike Gebert]

Anyone else seeing anything like this?

I think I'm getting it also - it appears to be a new Firefox "feature" and pops up when I'm using logins saved in Firefox to auto fill the login fields. Instead of immediately filling in the logins like it used to I now have to select the login ID from below the message before it drops in the info. Does it on other sites as well where I have saved logins. Probably useful info for the deeply paranoid, but I filed it under "Upgrades, Benign/Annoying."

No slowness issues though.

Absolutely right: it's due to the Firefox update. Mike, here is the page explaining the situation:
https://support.mozilla.org/t5/Protect- ... ta-p/27861

Jim

I'm using the older v.48 of Firefox which does not pop up the warning, but displays a "connection is not secure" message if the info icon next to the url box is clicked.

Not being secure (a site that connects via http rather than https) has Google search "ranking" consequences, among other things.

[silentfilm]

Jim, all you have to do is go to https://www.nitrateville.com instread of http://www.nitrateville.com or nitrateville.com. This will ensure that you always have a secure connection. If you have a bookmark for Nitrateville, make sure that you update it.

The new Firefox update has caused us headaches at work, because it no longer supports the java plugin. The good news is that you are protected from malicious viruses through Firefox. The bad news is that some web pages won't work the same.

* Tsk *

There you go again, Bruce, trying to make my life easier.

It worked. Have you no shame, sir?

Thanks!

Jim

One bit of helpful info for them's what have made the change to "https," if you want to see embedded YouTube links in a post you have to take the "s" out and just use "http" in the address bar. Was a bit baffling for a moment seeing large gaps in posts and folks talking about invisible videos.