Error Log – Bulletproof Error

This file: /bulletproof-security/admin/mod-test/mod_authz_core-nc-denied.png is just a diagnostic/testing file for the BPS Apache Modules|Directives|Backward Compatibility(Yes|No)|IfModule(Yes|No) checking code and files, which does a Live check using an htaccess file in this BPS testing folder: /bulletproof-security/admin/mod-test/ to check what your website/server does and does not allow/use regarding htaccess code. The HTTP Status code results of the diagnostic/testing htaccess file are used by BPS to create customized htaccess files and code for your actual Live BPS root htaccess file. So the 403 error is a normal/expected result/response and means that your server uses the Apache mod_authz_core module and relative directive htaccess code. The 403 error is not related to your site going down.

• This reply was modified 7 years, 11 months ago by AITpro.

Thanks, but I’m confused — so what is the importance of this mod-test folder and testing the htacess file in that folder which isn’t actually our live htaccess file?… in layman terms? Also, we received a 503 error at 8:59am-9am today EST and the cpanel error log reported the below as the only error during that same exact time:

[Tue Dec 13 08:59:42.155003 2016] [authz_core:error] [pid 22028:tid 140469948311296] [client 198.46.85.147:57090] AH01630: client denied by server configuration: /home/dequakerchem/public_html/wp-content/plugins/bulletproof-security/admin/mod-test/mod_authz_core-nc-denied.png, referer: https://de.quakerchem.com/wp-content/plugins/bulletproof-security/admin/mod-test/mod_authz_core-nc-denied.png

Thanks for your time.

The php error was a coincidence or secondary error to whatever the root problem was at 8:59am-9am today EST. Example: Your server hiccuped or had some other problem (connectivity, DNS, etc), which then caused the php error for the BPS Apache Mod testing file/code.

The importance or “pre” testing what/which htaccess code does and does not work on your website/server before BPS creates Live htaccess files for your website/server is that BPS will only create custom htaccess code for your Live htaccess file based on what your particular server does and does not allow/work with. The importance of continuing to check what htaccess code does and does not work on an ongoing basis factors in that someone might switch web hosts. If the new web host server does not allow or work with htaccess code that worked previously on your old web host then BPS will automatically create new custom htaccess files/code for your new host server when your run the BPS Setup Wizard again. Anytime you switch to a new web host you need to re-run the Setup Wizard again.

Additionally, the BPS System Info page checks Apache Modules|Directives|Backward Compatibility(Yes|No)|IfModule(Yes|No) in real-time when you view/access the BPS System Info page. That is primarily a real-time troubleshooting feature.

Additionally, if a problem is detected with self-protection htaccess code/files in the BPS plugin folders then new self-protection htaccess code/files will be created automatically.

[nodupe99] Assuming all questions have been answered – the thread has been resolved. If you have additional questions about this specific thread topic then you can post them at any time. We still receive email notifications when threads have been resolved.