Title: Solid Security causing error 404 Not Found Last modified: February 7, 2024 --- # Solid Security causing error 404 Not Found * Resolved [daaanvdb](https://wordpress.org/support/users/daaanvdb/) * (@daaanvdb) * [2 years, 4 months ago](https://wordpress.org/support/topic/solid-security-causing-error-404-not-found/) * Hi, * A bit more than a week ago, I had big problems with my website, which were eventually solved by deactivating the Solid Security plugin. * Here’s what went wrong: on my website the homepage loaded just fine. But if I clicked any other link (post, category, or just another url of my website), then I got the following error: * 404 Not FoundPlease forward this error screen to [http://www.daanvandenbroek.com’s ](http://www.daanvandenbroek.xn--coms -ib0e/); [WebMaster](https://wordpress.org/support/topic/solid-security-causing-error-404-not-found/webmaster@daanvandenbroek.com?subject=Error%20message%20[]%20%20for%20www.daanvandenbroek.com/cp_errordocument.shtml%20port%20443%20on%20Monday,%2029-Jan-2024%2016:35:17%20EET). * The server can not find the requested page: [http://www.daanvandenbroek.com/cp_errordocument.shtml](http://www.daanvandenbroek.com/cp_errordocument.shtml)( port 443) * With help of my webhosting, I found out that the Solid Security plugin was the problem (For a more extensive description of the problem, check the following topic: [https://wordpress.org/support/topic/www-daanvandenbroek-com-cp_errordocument-shtml-port-443/#post-17406744](https://wordpress.org/support/topic/www-daanvandenbroek-com-cp_errordocument-shtml-port-443/#post-17406744)) * Until then, I only had positive experiences with iThemes Security and it’s follow up plugin. However, this was a vital problem that I do not wish to have again. Do you have any idea what could have caused this, and how I can safely start using Solid Security again, without it causing this problem on my website? * Best regards, * Daan * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fsolid-security-causing-error-404-not-found%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 3 replies - 1 through 3 (of 3 total) * [nlpro](https://wordpress.org/support/users/nlpro/) * (@nlpro) * [2 years, 3 months ago](https://wordpress.org/support/topic/solid-security-causing-error-404-not-found/#post-17415787) * Hi [@daaanvdb](https://wordpress.org/support/users/daaanvdb/), * Most WordPress envs have no problems writing to the server configuration file(. htaccess file for Apache). Nevertheless I do sometimes see similar problems reported on this forum and the only way (so far) to “prevent” it from happening is to disable the **Write to Files** setting (enabled by default) and manually add the rules to the server configuration file (or not at all). * Next week I’ll be running some tests related to the **Write to Files** setting. I’ll be focusing on the setting being enabled by default, which (if my memory serves me correctly) wasn’t the case in the past. Depending on my test results I may contact SolidWP and request them to add the **Write to Files** setting to Step 2 of the plugin initial setup (see the picture below). That way you can opt-in (or not) during setup (which even without testing already makes a lot more sense). * ![](https://i0.wp.com/solidwp.com/wp-content/uploads/2023/09/configure-global- settings.jpg?ssl=1) * +++ To prevent any confusion, I’m not SolidWP +++ - This reply was modified 2 years, 3 months ago by [nlpro](https://wordpress.org/support/users/nlpro/). * Plugin Support [chandelierrr](https://wordpress.org/support/users/shanedelierrr/) * (@shanedelierrr) * [2 years, 3 months ago](https://wordpress.org/support/topic/solid-security-causing-error-404-not-found/#post-17436052) * Hi @daaanvdb, checking in here to see if you’re still getting the 404 errors on your site pages. * If you are, please try disabling the **Write to Files** setting in **Security > Global Settings** to prevent crashes when Solid Security automatically writes to the server files. Then, manually add the rules to your `wp-config.php` and`. htaccess` files. You can see the generated rules in **Security > Tools** **>**** wp-config.php Rules** and **Server Config Rules**. * Tracking notifications on this forum can become tricky over time, and due to inactivity, I’ll be marking this post resolved. If you still require assistance, feel free to let us know, and we’ll keep digging into this. Thank you! * Thread Starter [daaanvdb](https://wordpress.org/support/users/daaanvdb/) * (@daaanvdb) * [2 years, 3 months ago](https://wordpress.org/support/topic/solid-security-causing-error-404-not-found/#post-17474655) * Hi @shandelierrr and [@nlpro](https://wordpress.org/support/users/nlpro/), sorry for the late reply – I haven’t had the time to look into this more lately. For now I had the app inactive, which of course solved the problem for now. * Of course, I want to make sure to have a security plugin on my website. So I will try activating it again, but disable the Write to Files setting. Will this still provide the same level of security? * Best, * Daan Viewing 3 replies - 1 through 3 (of 3 total) The topic ‘Solid Security causing error 404 Not Found’ is closed to new replies. * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351) * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/) * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq) * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/) * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/) * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/) * 3 replies * 3 participants * Last reply from: [daaanvdb](https://wordpress.org/support/users/daaanvdb/) * Last activity: [2 years, 3 months ago](https://wordpress.org/support/topic/solid-security-causing-error-404-not-found/#post-17474655) * Status: resolved