Just checking in to ensure that the blog and comments are still working for everybody after some fixes this morning.
I got an email from Freedom Feen MWD, warning me that, on the Chrome browser at least, all HTTP sites will soon be labeled “insecure” — which, he notes, is a good development. But which will also discourage people from visiting those sites.
I thought both the blog and ClairesCabal.com were set up for HTTPS. But while the Cabal was properly showing that “s” in its address line, not so with the blog.
Turned out we had a twofold problem. Bear Bussjaeger checked and discovered that the SSL certificate for the blog site was present but had somehow ended up uninstalled. And MWD found a WordPress issue and guided me through a fix for that.
So, thanks to Bear and MWD … when you come to this blog, you should now see HTTPS in the address line AND you should not get any “insecure” messages if you attempt to log in.
It’s working that way for me. But we’ve had certificate issues before. Now, is all well and good for you guys?