Thread Starter
sally
(@sallyruchman)
When I go to System Info PHP Server is see this
PHP Version: 7.1.15
PHP Memory Usage: 35.83 MB
WordPress Admin Memory Limit: 320M
WordPress Base Memory Limit: 320M
PHP Actual Configuration Memory Limit: 100MB Recommendation: Increase Memory Limit to 128M.
PHP Configuration File (php.ini): /etc/php71-fpm.d/php.ini
Thread Starter
sally
(@sallyruchman)
Hello,
the Provider wrote me, that he deactivated the PHP-FPM Handler, and that he see on his side the error: configuration error: couldn’t perform authentication. AuthType not set!
I installed bulletproof security new, and when I started the Setup Wizzard all was green and good to go. After activation the frontend was available, but in the backend I get the error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, admin and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
What can be the problem??
Can anyone help me
Thx
Plugin Author
AITpro
(@aitpro)
This type of problem is going to require assistance from your web host support folks. I believe there is some sort of server/BPS incompatibility thing going on or maybe some changes in the server’s httpd.conf file would do the trick. You can try manually deleting the BPS root and wp-admin htaccess files to see if the site comes back up. If that works then that tells you that there is a server config/compatibility issue/problem with some or all of the BPS htaccess code in either the root or wp-admin htaccess files. The 500 error could be caused by this really old known issue/problem below.
https://forum.ait-pro.com/forums/topic/read-me-first-free/#bps-free-general-troubleshooting
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
Thread Starter
sally
(@sallyruchman)
Hello,
can I add the codes to custom code, or should I directly edit the .hta ?
Thx
Thread Starter
sally
(@sallyruchman)
Added the first #Options -Indexes to custom code, this was the issue 🙂
Thanks a Lot!
Best Regards
