Tagged: BPS Free General Troubleshooting
November 5, 2012 at 10:26 am #34
AITpro AdminKeymasterWeb Host Compatibility Check
BPS and BPS Pro are compatible with the 20,000+ Web Hosts worldwide, but are not compatible with these 3 Web Hosting Companies (Landis Holdings, NTT Communications & Yahoo Hosting – Due to Custom Server Configurations and/or Server Restrictions)
Symptoms of the problem: The htaccess Core page will not fully load and is “chopped off”.
Hostingzoom (Landis Holdings)
Resellerzoom (Landis Holdings)
Modvps (Landis Holdings)
WowVPS.com (Landis Holdings)
JaguarPC (Landis Holdings)
Verio (NTT Communications)
NTT America (NTT Communications)
NTT Europe (NTT Communications)
Yahoo HostingcPanel Hotlink Protection Tool – No Longer an Issue/Problem: BulletProof Security AutoMagic Not Working, Unable to Edit .htaccess Files, 404 Errors, 403 Errors, 500 Errors, Quarantine Not Working, Permalinks broken, menus broken, WordPress is broken in generalSolution: No Longer an Issue/Problem: The cPanel HotLink Protection Tool problem causes a large variety of problems. If you are unable to activate .htaccess files or edit .htaccess files with the built-in htaccess file editor or you are seeing 404 errors, 403 errors, 500 errors, permalinks are broken, menus are broken or WordPress is broken in general then most likely this is caused by the cPanel HotLink Protection Tool.
This issue/problem can be caused by the Broken cPanel HotLink Protection Tool problem or if another plugin or theme is using the WordPress flush_rewrite_rules() function incorrectly or also if your Server API type is DSO (see DSO Server Type help information below). You can check/find your Server API type on the BPS System Info page.Try refreshing your Browser first to see if the BPS alerts go away. These alerts could be left over from the previous check / last function check.
Important Note: The Lock htaccess File button not only locks the root .htaccess file for protection, but this also protects BPS / your website from plugins that are using the WordPress function – flush_rewrite_rules() incorrectly. This particular WordPress function is very misunderstood and is used incorrectly in a lot of plugins and of course causes a lot of problems for other plugins that create or write .htaccess code such as BPS, BPS Pro, W3 Total Cache, WP Super Cache, etc etc etc. The WordPress flush_rewrite_rules() function should ONLY be used in plugin deactivation and plugin activation functions.
Eliminating the possibility of a plugin conflict (flush_rewrite_rules() function used incorrectly):
1. Deactivate all of your plugins except for BPS.
2. Activate BulletProof Modes again.
3. Refresh your Browser.
If the problem IS still occurring at this point then it is NOT being caused by another plugin using the WordPress flush_rewrite_rules() function incorrectly.
If the problem is NOT occurring again then be sure to lock your root .htaccess file and turn on AutoLock on the htaccess File Editor page before activating your plugins again or the same problem will occur again and your root .htaccess file code will be deleted again by the WordPress flush_rewrite_rules() function in whatever plugin or theme that is using this function incorrectly.
If you lock your root .htaccess file and your Host does not allow locking the Root .htaccess file with 404 file permissions then your website will crash or your Host will automatically change the locked (404 file permissions) root .htaccess file to unlocked (644 file permissions). If your website crashes then FTP to your website root folder and change the root .htaccess file permissions from 404 file permissions to 444 file permissions. Some Hosts allow 444 file permissions, which is more secure than 644 file permissions and your root .htaccess file will be locked to prevent the WordPress flush_rewrite_rules() function problem from occurring repeatedly. If 444 file permissions are not allowed on your Host then unfortunately you will have to activate BulletProof Modes again each time this problem reoccurs or try contacting the plugin or theme author regarding this issue or modify the code in that plugin or theme.
NOTE: If your Root .htaccess file is unlocked and you go to the WordPress Permalinks page your Root .htaccess file code will be deleted. You will need to activate Root folder BulletProof Mode again.
500 Internal Server Error After Activating BulletProof Mode for your Root Folder
Some Web Hosts do not allow you to use the “Options” Directive in .htaccess files. If you see a 500 Internal Server Error then comment out the “Options” Directive by adding a pound sign (#) in front of Options -Indexes in your Root .htaccess file as shown below.
# DO NOT SHOW DIRECTORY LISTING # If you are getting 500 Errors when activating BPS then comment out Options -Indexes # by adding a # sign in front of it. If there is a typo anywhere in this file you will also see 500 errors. #Options -Indexes
Some Web Hosts do not allow you to use the “DirectoryIndex” Directive in .htaccess files. If you see a 500 Internal Server Error then comment out the “DirectoryIndex” Directive by adding a pound sign (#) in front of DirectoryIndex in your Root .htaccess file as shown below. Known Hosts with this issue: NordNet
# DIRECTORY INDEX FORCE INDEX.PHP # Use index.php as default directory index file # index.html will be ignored will not load. #DirectoryIndex index.php index.html /index.php
If you have added custom .htaccess code to BPS Custom Code, saved it, clicked the AutoMagic buttons and activated BulletProof Modes and there is either invalid .htaccess code in that custom .htaccess code or your particular Server/Host does not allow something in that custom .htaccess code then your site will crash with a 500 Internal Server Error.
1. Use FTP or your web host control panel file manager and delete your root .htaccess file (or the wp-admin .htaccess file if the custom .htaccess code was added to wp-admin Custom Code).
2. After you have deleted the .htaccess file or files, login to your site, go to BPS Custom Code, cut (NOT copy) the custom .htaccess code you added to any BPS Custom Code text boxes and paste that custom .htaccess code to a Notepad text file (use Notepad or Notepad++ – do NOT use Word or WordPad) and save it on your computer.
3. After cutting all custom .htaccess code that you have added to any BPS Custom Code text boxes, click the Save Root Custom Code button (and/or Save wp-admin Custom Code button), go to the Security Modes page and click the Root folder BulletProof Mode (and/or wp-admin Folder BulletProof Mode) Activate button.
Your site should not crash at this point with a 500 Error. You can then check and test your custom .htaccess code individually. ONLY add one section of your custom .htaccess code at a time to BPS Custom Code text boxes (and do ALL the Custom Code steps) to isolate which custom .htaccess code is causing the 500 error. Either correct whatever needs to be corrected or just do not use the custom .htaccess code on your website if it does not work / is not allowed on your particular Host/Server.
DSO Server Type: BulletProof Security AutoMagic Not Working/built in .htaccess File Editor Not Working, Unable to Backup or Restore Files
If your Server API type is DSO and your WP Filesystem API Method is NOT “direct” then you will need to do some additional setup steps for a DSO Server. You can check your Server API and WP Filesystem API Method on the BPS System Info page. If you see that your Server API is DSO and your WP Filesystem API Method is NOT “direct” then you will need to do these additional installation steps for DSO.
BulletProof Security WP Error: “no input file specified”- Permalink Problems/404 Errors – using the .html permalink hack is causing 404 Errors
If you see a “no input file specified” error then there is something wrong with your WordPress custom permalink structure. Another cause of 404 Errors is using the .html Permalink hack. Using .html in your WordPress Permalink Structure is considered a hack and is not a standard WordPress Custom Permalink Structure. Example Permalink .html Hack: /%postname%.html. Many years ago this supposedly increased page ranking and SEO. If that was ever really true it is definitely not true now. Using this permalink hack will only cause your website problems and BulletProof Security will not work with this permalink hack. You will need to change your custom permalink to a standard WordPress custom permalink structure in order to be able to use BulletProof Security.
403 Forbidden Error or 500 Internal Server Error when updating/upgrading BPS
Some web hosts (approximately 6 Hosts out of 1000’s of Hosts) have a strict policy that .htaccess files can ONLY have 644 permissions and do not allow you to change your .htaccess file permissions to 404. During the BPS automatic update/upgrade process your Server API is detected and if it is a typical SAPI that should allow your .htaccess file to be locked with 404 permissions then BPS will automatically lock the file. To see if this is the problem that is occuring FTP to your website and change the .htaccess file permissions in your website root folder to 644. If the 403 error goes away then please let us know which Host you have by posting a comment here so that we can add them to the below of Hosts that do not allow 404 file permissions for .htaccess files.
If your Web Host does not allow locking of your Root .htaccess file (404 file permissions for your Root .htacces file) and your site has crashed then FTP to your website and manually change the root .htaccess file permissions to 444. If your site is still crashed/not loading then change the root .htaccess file permissions to 644. After your site is back up go to the BPS htaccess File Editor tab page and click on the Turn Off AutoLock button. This will prevent your Root .htaccess file from being automatically locked when you upgrade BPS, which will prevent a 403 Error from occurring on your website.
List of Web Hosts that require 644 .htaccess file permissions – 404 permissions are not allowed on these Hosts and will cause a 403 Error and or 500 Internal Server Error – 444 file permissions may be allowed on these Hosts
If your Web Host does not allow locking of your Root .htaccess file/404 file permissions for your Root .htacces file, then go to the BPS htaccess File Editor tab page and click on the Turn Off AutoLock button. This will prevent your Root .htaccess file from being automatically locked when you upgrade BPS, which will prevent a 403 Error from occurring on your website.
StratoSeptember 14, 2015 at 10:26 pm #25003
Another host to add to the list of those not allowing changes to .htaccess file permissions is Webline Services http://webline-services.com/. To be fair, I haven’t tried asking them, as I am about to move my http://www.propertyforsalespain.co.uk/ website to a new host anyway. I have for the moment got around the 404 error by deactivating root folder bullet proof mode and wp-admin folder via BPS Security/htaccess Core in Admin.
You must be logged in to reply to this topic.