Plugin Author
AITpro
(@aitpro)
Most likely there is some bad/invalid htaccess code in one or more of the BPS Custom Code text boxes. Do these steps.
1. Use FTP or your web host control panel file manager and delete the BPS Root and wp-admin htaccess files.
2. Log into your website.
3. Go to BPS Root Custom Code and check all of your Custom Code text boxes for any bad/invalid htaccess code, delete it and click the Save Root Custom Code button.
4. Go to BPS wp-admin Custom Code and check all of your Custom Code text boxes for any bad/invalid htaccess code, delete it and click the Save wp-admin Custom Code button.
5. Go to the BPS Security Modes page and click the Root and wp-admin Folder BulletProof Mode Activate buttons.
Plugin Author
AITpro
(@aitpro)
If you are not sure about what bad/invalid htaccess code to look for in BPS Custom Code then use the Custom Code Export feature and send your Custom Code export zip file to us so we can take a look at your Custom Code: info at ait-pro dot com.
Ok, I deleted wp-admin htaccess. That by itself didn’t work and I cannot locate any BPS file. Search of the entire Blog directory turns up no matches for BPS.
Plugin Author
AITpro
(@aitpro)
The BPS root htaccess file would be in the same folder as your WordPress installation and the wp-config.php file. If you are using an FTP application to view files then make sure you have “show hidden files” checked/allowed/on. Some servers/websites need to have a root htaccess file or a 500 error will occur. So that could be the problem. Download this file from your website: /wp-content/plugins/bulletproof-security/admin/htaccess/default.htaccess. Upload the default.htaccess file to the same folder where you see the WordPress wp-config.php file and rename the default.htaccess file to .htaccess.
Plugin Author
AITpro
(@aitpro)
Also check this folder: /wp-content/mu-plugins/ and delete this file: bps-plugin-autoupdate.php if you see that file.
Great. That worked. Is there anything I should do when setting BPS back up or that I should do to avoid these issues in the future?
I’m able to get back into the site.
I found no errors pointed out in the custom code, but activating wp-admin Folder BulletProof Mode (WBM) triggers the error.
Plugin Author
AITpro
(@aitpro)
Ok now manually delete the wp-admin htaccess file again and then login and activate Root Folder BulletProof Mode. Does the Root htaccess file also cause the error? I would like to isolate the problem to either the wp-admin file or both the wp-admin and root htaccess files, which would then indicate an entirely different problem. Or there could be bad/invalid htaccess code in both htaccess files.
-
This reply was modified 8 years, 11 months ago by
AITpro.
Activating Root Folder BulletProof Mode (RBM) also seems to trigger the error in a delayed manner. I can see the home page, but once I click to the posts page the 500 error comes back.
Clicking the link to import All-In-One-SEO settings also triggers a 500 error.
Plugin Author
AITpro
(@aitpro)
Ok that means that either standard BPS .htaccess code is not allowed on your particular server or you have bad/invalid htaccess code in both htaccess files. Go to BPS Custom Code > click the Export button > send your Custom Code export zip file to: info at ait-pro dot com. If I do not find any bad/invalid htaccess code in your custom code zip file then you will need to contact your web host support folks, have them look at the BPS htaccess files and let you know what they do not allow on your particular host server/website.
Plugin Author
AITpro
(@aitpro)
Or you can just choose not to use BPS htaccess files on your server/website by going to the Setup Wizard Options page > Enable|Disable htaccess Files option > select htaccess Files Disabled > run the Setup Wizard again.
I had to re-upload my .htaccess file back to the wp-admin folder, which must have been why I was getting the error after activating WBM (no file). Now when I activate WBM then, there is no error. When I activate RBM the error comes back.
Plugin Author
AITpro
(@aitpro)
hmm I just saw your other post about “…import All-In-One-SEO settings also triggers a 500 error…” At this point you need to contact your web host support folks and ask them to check the server log files for why these errors are occurring. My guess would be that a Mod Security rule is causing the 500 errors.
