500 internal server error caused by “All In One WP Security”

There are other reasons that we could investigate, for example the following can cause a 500 error

External Resource Timeout

Sometimes the web server may need responses from a remote server to complete processing the request from a client. There can be situations that these external resources may timeout. This can be a php timeout. In such cases, the webserver will return a 500 Internal Server Error. We can fix this error by increasing timeout values or setting other appropriate timeout options so that the remote server will not return a timeout error but wait for the request to be processed.

Issues triggered by Wrong File and Directory Permissions

This is the cause of most Internal Server Errors. If the permission of one more file or directories needed to process the request of the client is set wrongly, it will not be accessible to the server so that the error is returned. The wrong permission of a php script is an example of this type issue. This issue can be fixed by resetting the correct permission on the file or directory.

Misconfiguration in .htaccess file

Another common cause of the 500 Internal Server Error is a misconfiguration in the .htaccess file. Errors in URL rewriting can lead to, but not often a 500 Internal Server Error. Locating and correcting the misconfiguration in the .htaccess file can fix this issue. You could try downloading a copy of your .htaccess and the re-creating it using this guide: https://www.hostinger.com/tutorials/locate-and-create-htaccess.

The best place to start would be your php logs (part of Apache error logs) for more information about the error. Your hosts might be able to help you with this.

If you are unable to find the error logs there, try enabling PHP error reporting by adding the following lines to the index.php file:

ini_set(‘display_errors’, 1);
ini_set(‘display_startup_errors’, 1);
error_reporting(E_ALL);
If you have a WordPress website, download the wp-config.php file (located in the website’s root directory) via SFTP and open it in your preferred text editor. Search for the string ‘WP_DEBUG’. If you find the line, simply change FALSE to TRUE and upload the file again.

If the line isn’t in the config file, add the following line to the wp-config.php file:

define( “WP_DEBUG”, true );`

If you could let us know what (if anything) is in your logs, we can start to rule certain issues out. I would also check your file permissions go rule this out.