FIXED 500 Internal Server Error on WordPress



FIXED 500 Internal Server Error on WordPress

Grab your free 17-Point WordPress Pre-Launch PDF Checklist:

The 500 internal server error is not a WordPress-specific error. It is a general server error that may be related to your server settings or your WordPress files. Use the information in this tutorial to troubleshoot the 500 internal server error you are receiving.

Here are the things you’ll need to troubleshoot.

1. Your htaccess file may be corrupted. Try renaming it and see if that fixes the 500 error. If it does then the problem is in the htaccess file.

2. You may have reached the memory limit on your hosting account. Try increasing the limit using one of the methods outlined in this tutorial:

3. Try replacing the wp-admin and wp-include folders with fresh versions of those folders. This one is more complicated. Basically you’d backup those two folders in your hosting account and upload those two folders from a fresh version of WordPress downloaded from WordPress.org.

Check Your Plugins

The first 500 internal server error troubleshoot is by deactivating all of your plugins.

To do this log into your site files using FTP or going through cPanel.
If you go the cPanel route, click on File Manager in your cPanel.

The find your website’s root folder. It is usually in the public_html folder.

Then navigate to wp-content and locate the “plugins” folder.
Next rename the Plugins folder to something different like “plugins-old”. This deactivates all the plugins on your site.

If that fixes the problem, then you know the problem is with your plugins.

Now that you know the problem is with your plugins you can go into the WordPress back-end and activate each plugin individually to isolate the cause.

You do this by activating one plugin, then reload your website. If you do not see the 500 Internal Server Error then it’s not that plugin.
Then activate another plugin and do the same until one of them breaks your site.

Once you know which plugin is causing the 500 Internal Server error, you can either delete that plugin, replace it, or contact the developer for more help.

If deactivating the plugins didn’t fix the problem, keep on reading.

Increase Your Memory Limit

The next step in the troubleshooting process is to increase the memory limit on your website.

Go cPanel and open the File Manager again. There may be a file in your website’s root called php.ini. If there is not just create a file with that name.

Now, open the newly created file in the code editor and type memory=128MB in the file. This should increase your memory limit.

Now refresh your website.

If the error is gone, the cause was a memory problem on the server and you have identified the problem.

You should now contact your host support to figure out what is draining your memory and remedy the problem with their help.

Replace wp-admin and wp-include Files

If increasing the memory limit did not clear up the error, then copy in a new “wp-admin” folder and “wp-includes” folder in your WordPress site.

This can be done quite simply, but you want to follow the right process to protect yourself in case anything goes wrong.

First, go to your root folder and compress each of the current “wp-admin” and “wp-includes” folders into a zip archive. Just in case something goes wrong you’ll have a backup of those files.

Now go to wordpress.org and click on the “Download WordPress” button.

The downloaded zip file will contain the latest versions of “wp-admin” and “wp-includes”. Unzip that WordPress file.

Find the “wp-admin” and “wp-includes” inside the WordPress folder on your harddrive. Highlight both of them and compress them.

Upload them into the root folder of your website using cPanel or FTP.
Now go ahead delete the uncompressed versions of these folders in your website root.

Next, extract the compressed folders and now you have fresh copies of them on your website.

Refresh your website to see if that fixes the problem. If it does fix the problem, you can safely delete the compressed backups.

Subscribe to this awesome channel here:

Nguồn: https://banglasemantics.net/

Xem thêm bài viết: https://banglasemantics.net/category/cong-nghe

40 thoughts on “FIXED 500 Internal Server Error on WordPress

  1. woohoo!!!!! THANK YOU SO MUCH!!! I AM SO THANKFUL FOR YOUR VIDEO!!! For me, it was installing the new admin and includes folders! You are awesome!

  2. i am facing "Your server is running PHP version 5.4.45 but WordPress 5.2.4 requires at least 5.6.20" issue. Went in to cpanel and there was no 5.6 found. Can you guide me?

  3. Hi, and thanking you for your help.

    Our frontend was working fine and back end coming up with 500 internal server error.
    From file manager I changed "Plugins-old" and this allowed access to the back end. While in there I updated the wordpress version and can access the back end after changing back to "plugins", however now the front end just comes up with a loading screen. All the plugins in the back end appear deactivated… any advice please and thank you? 🙂

  4. I'm so confused I'm just trying to checkout and pay for something yet I get this message on my phone, I really need help like in simple terms, thanks

  5. My Problem is that, when i updating wordpress page it not successfully update, it turns out a white blank page. then when i check on console, it says "Failed to load resource: the server responded with a status of 500 (Internal Server Error)". i hope you can help me. i already done checking htaccess and memory limit, nothing happen.

  6. The site is experiencing technical difficulties. Please check your site admin email inbox for instructions.

    I am install woocommerce plugin then type of error will come plz help me and make one video

  7. Hi my friend i have a problem on my website
    When i open it
    Tell me that it's not reachable
    So i always use vpn
    I try to reset dns ip every thing proxy
    Unistalling goole chrome
    But it's not working

  8. Was becoming worried when the first few ones didn't work for me…Until 6.30 minutes, .htaccess file worked perfectly. Thanks; you saved a life

  9. Turns out it was my htaccess file and making a new one solved the problem. However if I copy the code from the old one, then the error message comes up again. How do you work out which code line is corrupt? Otherwise is there a way to regenerate that code? Thanks

  10. Really nice video really informative, but when I had this problem it was an error 404 first then I asked my hosting provider to assist in which they did but it brought me to this now error 500, the hosting provider then told me to update my permalinks but even after that my problem still continued. What do you think is a good solution because I tried the first 3 of your solutions with no luck, I have even thought about deleting all the WordPress files and starting over.

  11. Hi mate, your video was very interesting. Actually, I tried all the steps you provided but still no changes. Can you please assist?
    Thank you

  12. Le serveur a rencontré une erreur interne ou une mauvaise configuration et n'a pas pu traiter votre demande.

    Veuillez contacter l'administrateur du serveur à l'adresse pour l'informer de l'heure à laquelle cette erreur s'est produite et des actions que vous avez effectuées juste avant cette erreur.

    Plus d'informations sur cette erreur peuvent être disponibles dans le journal des erreurs du serveur.

    En outre, une erreur 500 Internal Server Error s'est produite lors de la tentative d'utilisation d'un ErrorDocument pour gérer la demande.

  13. une erreur 500 Internal Server Error s'est produite lors de la tentative d'utilisation d'un ErrorDocument pour gérer la demande.

  14. heeloo, i have error remote.
    wp_remote_post() failed. Contact your hosting provider. 400
    why this happen, and how to fix it. thanks

  15. I tried renaming plugins to 1plugins, and nothing. I don't have htaccess in the filezilla. My website was working, then just shows HTTP ERROR 500

  16. Unfortunately, none of these fixes worked for me. In the end, I was able to find the problem in cPanel by finding error_log in public_html and looking at the fatal error that was causing the problem. The problem was that my active theme was broken, so I found and deleted the theme file. For anyone who is having problems that aren't solved by this video, I'd recommend looking at the error log.

Leave a Reply

Your email address will not be published. Required fields are marked *

Theme: Overlay by Kaira Extra Text
Cape Town, South Africa