BulletProof Security Forum

Actually since you have moved your wp-config.php file to another folder I will not be able to manually edit it.  If you are not that concerned about logging php errors then you can turn off the “PHP Error Log Path Does Not Match” error check on the BPS Pro > S-Monitor page > PHP Error Log: Check Folder Path Location Alert option setting > change…[Read more]

Ok at this point send me a WordPress Administrator login to this website to email:  info at ait-pro dot com.

So copied the wp-config file as requested and the Set Up wizard came back with all green comments, no red errors.

Then copied it back and deleted it but the ARQ keeps putting it back so have turned that feature off for now.

The PHP Diagnostic Checks  have the same error now I’ve moved the wp-config file again.

I;m not bothered about having…[Read more]

Try this first. Move your wp-config.php file back to where it is supposed to be in your WordPress installation folder and run the Pre-Installation Wizard and Setup Wizard. If that fixes the problem then you can move your wp-config.php file back to the folder where you have moved it to.

Thanks. Diagnostic check results below.

PHP Version: 7.2.25
PHP|php.ini Handler: A PHP|php.ini Handler was Not found in your Root .htaccess file.

Configuration File (php.ini) Path: Click the View PHPINFO button on the PHP Info Viewer page to get this path.
Loaded Configuration File: /etc/php72.ini.d/php.ini

php.ini, php5.ini & .user…[Read more]

Go to BPS Pro > P-Security > PHP.ini Options tab page and run the Diagnostic Checks/Recommendations by clicking the Run Check button. Post the information that you will see in the Diagnostic Checks window in your forum reply.

Okay, thank you for the response. We’ll try this out across our sites when we have the time and see if this resolves the issue.

Nicolas from Living Miracles

See this forum topic for the solution > https://forum.ait-pro.com/forums/topic/whitelist-monarch-plugin/#post-37359

Create an HPF ignore rule for this additional plugin folder created by the GoUrl Bitcoin Payment Gateway & Paid Downloads & Membership plugin.  I tested the plugin and when you install and activate the plugin it creates this additional plugin folder: /gourl-php/. The HPF checking code sees this as a possible illegitimate/malicious plugin folder…[Read more]

If your web host malware scanning service is free or reasonably priced then it does not hurt to have it as an additional security measure.

Thank you! You are the BPS god 🙂

I’m going to go ahead and leave a stellar review for the BPS Pro plugin. Also, do I need automatic file scanning with Malware clean up with my hosting company since I have BPS Pro?

I edited out the standard default WordPress Rewrite htaccess code because BPS htaccess code already incorporates that code.

1. Copy the code below into this BPS Root Custom Code text box: 1. CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
2. Click the Save Root Custom Code button.
3. Go to the BPS Security Modes page and click the Root Folder…[Read more]

Thanks for the quick reply
Below:

# Compress HTML, CSS, JavaScript, Text, XML and fonts
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/vnd.ms-fontobject
AddOutputFilterByType DEFLATE application/x-font
AddOutputFilterByType DEFLATE…[Read more]

BPS has a feature called Custom Code (BPS Pro > B-Core > Custom Code tab page) where you can save any custom, personal or additional htaccess code permanently and that custom, personal or additional htaccess code will be created in your root htaccess file. What htaccess code was overwritten? A backup of your root htaccess file is automatically…[Read more]

Login page error:
My first attempt to login to your site I saw this error message below:
ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.

I believe the Login page cookie problem is being caused by Cloudflare Rocket Loader.
You probably need to create a Page Rule in your Cloudflare dashboard…[Read more]

Yep, way back there was a bug in older BPS plugin versions that caused problems with the root htaccess file during the update to a newer BPS plugin version. That bug was fixed in later versions of BPS and that problem no longer occurs.  I received your direct email to us and have responded to your email.