Day: September 6, 2024
Oh no! It seems we can't find what you're looking for. Please try again
By default the debug.log file is written to a standard folder and filename: /wp-content/debug.log This standard will be available on 99% of the websites. And because /wp-content/ is a publicly accessible folder (It also has your uploads folder with images, for example), the debug.log might be an interesting file for anyone with malicious intent, if accessible. But why? The debug.log might contain important or confidential information. If it extends to plugins that handle more sensitive data like usernames, passwords, emails, payment credentials,
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
Security headers are a powerful way to strengthen SSL and to further secure the connection between site visitors and the webserver. Security Headers can be considered ‘instructions’ for the webbrowser. For example, the X-Frame-Options header will tell the browser if the page or site is allowed to be loaded in an iFrame. We will discuss possible and recommended configurations for the four Recommended Security Headers within Really Simple SSL Pro: The Recommended Recurity Headers block within Really Simple SSL Pro
If your site has a valid SSL certificate but is still reported as insecure in browsers, this could be because it contains “Mixed Content” (HTTP content loaded on a HTTPS website). The built-in Mixed Content fixer in Really Simple SSL will dynamically fix all of the Mixed Content in the HTML of your site. If you have the Mixed content fixer enabled, but your site is still marked as insecure: you possibly have a type of mixed content that could
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