What is a WordPress 500 error?
Whether it’s a site update or a first CMS installation on the host, the 500 WordPress error can occur at any time. Do not panic, because it is a mistake like the others. A 500 WordPress error is none other than an internal server error frequently encountered on WordPress sites, but also on other sites. A 500 Internal Server Error error message appears immediately on your site when this occurs. Many causes can lead to it: the error of configuration of the .htaccess file, the contradiction of the sessions, the very slow loading of the site, the addition of a new file or a new file on the server or to use too much a lot of resources on the server. This message also appears in case of misconfiguration of a theme or plugin. There are still other causes, but what has just been mentioned here is the most common. To be able to repair them quickly and efficiently, one must first discover their origin.
At every error 500 WordPress its way to repair!
The WordPress 500 error may appear at any time. You should not be surprised when you encounter this problem. Of course, this error can panic a beginner in WordPress. On the other hand, the more you panic, the more important the problem will seem to you. The first reflex you have to face in such a situation is to find the cause that might well trigger that error. Once the origin is detected, you can proceed to the repair by following these advises:
- In case of the bad configuration of the .htaccess file, you have to look for this file on the server of your WordPress site. Once found, simply rename the file to old.htaccess and the error will be corrected automatically in 90% of cases. If the repair did not succeed, you can switch to other techniques.
- Check if a new file or folder has been added to your server. If this is the case, simply change its authorization number by right-clicking on the found file. The authorization number is 644 for a file and 755 for a file.
- The other technique is dedicated to repairing an error that occurs intermittently as a result of the slow loading of the site. In this case, you must first remove all active sessions from your browsing history from your website. In some cases, this is enough to solve the problem. Otherwise, it is recommended to check the error logs and look for the source of error 500 so that you can check the resource usage on the FTP server. If none of these solutions are retained, do not hesitate to ask the help of your host. Simply open a technical ticket via the “support” section of your customer area. Thanks to the server logs he keeps, he is perfectly entitled to get to the bottom of things.
Fixed 500 WordPress errors, other methods to adopt!
The first thing to do to fix a WordPress 500 error the first time is to check the .htaccess file. When you have changed the file name, load the site to see if everything is set or not. In case of failure, it is advisable before going to the “Parameters” then to the “Permalinks” present in your WordPress dashboard. Then click the “Save” button to create a new file.
Among the other methods, you need to adopt to fix a 500 WordPress error is increasing the size of the PHP memory limit. Note that this type of error may be displayed if your PHP memory limit is exhausted. To increase the size of the PHP limit memory, the first thing to do is to create a blank text file called php.ini. Then, you paste this code into the memory = 64MB file. After saving it, start the download in your / wp-admin / via the FTP folder. If the memory limit is exhausted, it means that there is something that consumes a lot of your memory. This remains to be determined so that the problem of this kind does not repeat itself. Be aware that this can be a theme function or a badly coded plugin. Only your hosting company can help you perform accurate and accurate diagnostics by consulting the server logs.
The importance of disabling all plugins in case of 500 error in WordPress
If none of the solutions mentioned above are effective, it probably means that the problem is caused by a specific plugin. As this will be difficult to detect, disabling all WordPress plugins at the same time is the best solution. Then activate the extensions one by one until you find the plugin that caused the error. Once detected, delete it and do not forget to report it to its author. If this option to disable the extensions could not correct the error, you can return the base files, that is, change the WP-includes and wp-admin files with new ones. This can be useful if a file has been corrupted.
If you are unable to resolve the 500 Internal Server Error with these different methods, contact your web host who can debug the problem faster and more efficiently. It is important to inform your host of all the steps and techniques you have tried to solve your problem.