During the last couple of days, your browser may have blocked access to the site after returning an error message warning you that the site isn’t secure. There’s a reason for that, and I’m going to explain it now because what I’ve been trying to do has been fraught with problems that I’m blaming Google for getting me into.
Google Chrome is currently the most popular browser in the world. Last October, version 62 was released. It includes a new feature that marks non-secure websites as such in the address bar. Any HTTP pages that collect data (login details, financial or banking info, search queries, registrations, etc.) are now marked as “Not Secure”. That includes this site. I don’t use Chrome and didn’t learn about the feature myself until last week. I don’t want Chrome users visiting the site for the first time getting spooked, especially considering the nature of the content here.
The site doesn’t have a registration form. I discontinued member logins after moving to WordPress four years ago. The Login page on the lower right only serves as my access to the site’s Control Panel. The Comment form does require an e-mail address to thwart spam bots, and that field is what I’m trying to protect by adding a Secured Socket Layer (SSL) certificate to the site. SSL is the standard security technology for establishing an encrypted link between a web server and a browser. This link ensures that all data passed between the web server and the browser remain private and integral. I added it to my 3D art message board at Visions of Darkness last month in response to user feedback to keep account information safe and it works beautifully. In stark contrast, adding it to Cinemasphyxia’s WordPress installation has become a massive headache. So, I’ve removed SSL until I figure out a solution.
I welcome and invite comments on my blog posts but I’ve disabled them until further notice. If I can’t get SSL to work, they’ll remain disabled and all future communication will have to be done via email.