Article-features-+-Assets Back

500 Internal Server Error

If you’ve spent much time browsing the internet, you’ve definitely run into a 500 internal server error. These mistakes don’t just happen with WordPress. They are general mistakes that don’t reveal anything about the actual reason. Don’t worry. These mistakes, which have been faced by many people, can be solved. In fact, we regularly solve them.

There are five main causes of these WordPress errors: 

  1. Incorrect web server configuration
  2. Incorrect folder/file permissions 
  3. Corrupt files or files that contain errors in code 
  4. PHP memory limits set too low 
  5. Conflicting third-party plugins

Incorrect web server configuration

Incorrect web server configuration 500 Internal Server Errors might happen if the directives on your web server (Apache or IIS) are configured incorrectly. The issue is that web hosting support frequently blames for errors on third-party applications you have installed without even looking at their error logs. You should persuade your web provider to help identify and address the issue once you have identified the remaining causes.

Incorrect folder/file permissions

The default file permission settings for WordPress, plugins, and themes should be 755 for folder and 644 for files, with very few exceptions. You could believe that loosened permissions, such as 777, will solve the issue, but you’d be mistaken. Setting permissions that are either too strict or too loose usually result in several errors afterward.

Corrupt files or files that contain errors in code

It typically results from inaccurate file transfers to the web server. The file may remain, but a number of errors may occur because the server cannot access the file. For example, if you uploaded a text file in binary instead of ASCII, the web server won’t be able to read it. This issue can be caused by coding errors in WordPress, a plugin, or a theme.

  • Reinstalling WordPress is the best method to fix a core WordPress error.
  • Deactivating all plugins will fix the issue
  • Removing and installing the theme will frequently solve the issue if it is theme-related.

The WordPress’s .htaccess file is responsible for the most common of 500 errors. This file was created primarily for usage with unique permalink structures. However, some third-party plugins also use it, and if permitted, it may be used to override specific server configuration directives. It may give the dreaded 500 internal server error if it has issues

  • Log into your site via FTP (Filezilla, etc.)
  • Create a backup of your .htaccess file by downloading it and renaming it “.htaccess-backup.”
  • Delete the .htaccess file residing on your Web server
  • Create a new blank file called “.htaccess” on your PC/laptop/Mac
  • Upload this new file to your Web server in the same place as the old one(which you deleted)
  • Log in to your WordPress’s Admin Dashboard
  • Go to the Settings> Permalinks> Save changes

PHP memory limits set too low

You can request your web host to increase your PHP limits or upload your theme via an FTP client.

You can read our article to learn more about it

Conflicting third-party plugins

Frontend Error

  • Login to your Admin dashboard and deactivate all plugins.
  • Check your front-end page once more after that. If it loads without error, there is a plugin conflict.
  • Start activating each plugin one by one.
  • The plugin you enabled is mainly responsible if you have the 500 issues on the front-end sites again.
  • Deactivate it and make sure there are no more errors by checking each of the other plugins

Backends and Fronted Error

  • Access your site via an FTP client.
  • Changing the temporary name of your /wp-content/plugins folder to anything different, such “plugins.bak,”. WordPress will ignore your plugins as a result.
  • If the error keeps occurring, change your plugin after logging into your admin area
  • Deactivate all of your plugins via your admin page.

Recommended PHP configuration limits are as follows:

  • Max_execution_time 600
  • Max_input_vars 10000
  • Memory_limit 256M
  • Post_max_size 100M
  • Upload_max_filesize 100M
  • cURL: 7.4 or higher
  • Zip PHP Module Enabled
  • allow_url_fopen Enabled
  • By installing a simple plugin provided here, you may check the PHP configuration limits. Additionally, you may always get in touch with your host to find out what the current settings are and request that they make any necessary adjustments. However, many hosts will make an effort to keep the PHP restrictions low.

$55