Category: Troubleshooting
How to debug a blank settings page in Really Simple Security
If you can’t view your settings in Really Simple SSL, but see a blank page instead, there are some common causes you can check. Plugin conflict One of the first things to check is whether the issue persists with Really Simple SSL (Pro) as the only activated plugin on your website. If this resolves the issue, one of the currently deactivated plugins was very likely related to the issue. A quick way of doing this is by using the Health
HTTP status codes (Server 500 or 404 errors)
Unfortunately, we all come across a 404 error from time to time. It is the most well-known HTTP Response code (or status code). The HTTP response code is a response from the server to the client, which usually is the site visitor’s browser. The response codes are categorised and can be recognised by the first digit. We’ll then list the most common and relevant response codes. 100 informational response It is not likely that you’ll ever see this as an
Locked out after renaming the admin username
When attacking WordPress websites, guessing usernames and passwords is still a commonly used method to gain access to a WordPress back-end. It goes without saying, that using easy to guess passwords like ‘12345’ or ‘Welcome2022’ will make it really easy for attackers to login to your administrator account. The same goes for usernames; using easy to guess usernames like ‘Admin’ will make it too easy for attackers. This is why Really Simple SSL allows you to prevent usage of the
Debugging issues with Really Simple Security
Really Simple Security will work fine out of the box in 99% of cases. There is, however, a slim chance you might need to debug an issue with the plugin. We have created articles for each of the most common problems that could arise when using Really Simple Security. We’ll start with the most common issues. Troubleshooting Really Simple Security Issues related to lock-outs It could be that you accidentally locked yourself out due to a security feature in the
WP Config fix needed
In some cases, your wp-config.php will require some adjustments before the site works correctly over SSL. This usually happens when your site is behind a loadbalancer, or if your wp-config.php contains a hardcoded http:// URL in the WP_HOME or WP_SITEURL constant. Really Simple Security will fix this automatically in most cases, but fails if the wp-config.php file is not writable. To automatically fix this issue, make your wp-config.php file writable. Alternatively, you can do the following to manually fix this issue: