Category: SSL & HTTPS
When the built in deactivation does not work, manual uninstalling
Installing SSL can be tricky. For instance, if another plugin redirects to http or your SSL certificate is not valid; a redirect loop could occur, resulting in an inability to access the back-end. This plugin is shipped with a simple way to deactivate remotely, without access to the back-end. While this should always work, as a fall-back, this article describes how to manually revert to HTTP. To know what we have to do, we have to know what the plugin
Does the plugin do a SEO friendly 301 redirect?
When you enable a 301 redirect with Really Simple Security, the SEO value (commonly referred to as “link juice”) is transferred to the new destination URL, so that the site maintains its ranking potential in search engines. By default, when clicking Activate SSL in Really Simple Security; a 301 internal WordPress permanent redirect is added, which means that the redirect is handled by WordPress. If you are running an Apache or LiteSpeed webserver, you can enable a .htaccess 301 redirect
My browser still gives mixed content warnings
“Mixed Content” means that the site contains both secure (HTTPS) and insecure (HTTP) content. If your site contains Mixed Content, it may not load correctly over HTTPS as a result. The Free version of Really Simple Security contains a Mixed Content Fixer which dynamically fixes the most common types of mixed content. If the mixed content fixer is active, Really Simple Security automatically fixes all images, JavaScript, stylesheets, @import URLs and iFrames with http:// links. It does this without making
The settings page says redirect could not be set in the .htaccess
Your site can run on SSL without any issues. The plugin also adds some javascript to redirect any non https pages, so your site should load over https without any problems. Furthermore, you can enable the HSTS setting to improve security. Common causes: 1. The .htaccess is not writable, or not available. 2. Testing of the .htaccess rewrite rules failed. This can be caused by several things: The plugin couldn’t access the test page: some configurations do not allow access