This category contains posts which relate to our website and WordPress service offerings. They provide additional information and updates to policies and practices.
What are mixed content errors?
Mixed content errors are reported by web browsers when an SSL (Secure Socket Layer) certificate is installed and active for the website and domain, but content is still being loaded over the HTTP protocol.
When an SSL certificate is installed and configured for a website the protocol of the website is set to HTTPS. This indicates to the server that the data should be sent securely using the SSL to encrypt the data before it is sent to the server, and then to have it decrypted once it reaches the server. Sometimes, however, a website is setup to use the HTTPS protocol, but some assets on the website (such as images, or external assets such as libraries) may still be loaded over HTTP. If this is the case, the browser will display what’s known as a mixed content error.
Here’s an example of how Google Chrome reports a mixed content error:
To generate this error, I simply setup the BellinghamWP.com website’s logo to load over HTTP instead of HTTPS.
Due to a recent increase in malicious activity directed at websites with out-of-date software, it has become necessary for us to make modifications to our hosting services and rates. These modifications represent our ongoing effort to provide our clients with secure, professional hosting services.
Although it is true that hackers are working day and night to find security vulnerabilities to exploit in every CMS (not just WordPress), the good guys are doing their part as well. By issuing regular updates to the WordPress Core, WordPress Plugins, and WordPress Themes these web developers are actively patching potentially exploitable holes in security. These updates will not do any good if they are not installed, however. The Bellingham WP Managed WordPress Hosting service has been created as an affordable option to address these security concerns.