FREE SPEED AUDIT
FREE SPEED AUDIT

FIXED WordPress 500 Internal Server Error

written by WP Fix It

May 23, 2017

DAMM YOU WordPress 500 Internal Server Error

If someone gave you $500 for doing nothing, you would be so happy. But is if you saw a WordPress 500 Internal Server Error you would not be so happy. The good news is in the majority of these situations, it is very easy to fix. We want to run you through 5 things to isolate the WordPress 500 Internal Server Error and then the steps you can take after to fix it.


#2 MAKE SURE HOST IS CORRECT

So if your host tells you that the server is fine, you can take their word for it but we suggest you verify that statement. It is so simple to do so too. Using either FTP access or your web hosting file manager, you want to upload the file at THIS LINK. Make sure you unzip this file before you upload it. This will be uploaded to the root folder of your server and once that is completed, you will visit YOUR_DOMAIN.com/info.php. If the server is working as it should, this address should load and you will see some server info. If you still get a 500 Internal Server Error on WordPress, the server is not working and you can go back to the host and provide them this URL stating it should load as it is only a 1 line file that does not depend on anything to load.


#3 CHECK .HTACCESS FILE FOR ERRORS

This file is the soul of your server configuration and 1 simple wrong character in this file can quickly crash your site and cause a WordPress 500 Internal Server Error. A very quick and easy way to see if this is the issue is to connect to your site’s files using either FTP or your web hosting control panel and rename the file. If the site loads after that and the WordPress 500 Internal Server Error is gone, then you found the root cause. Simply login to your site and re-save your permalinks by going to SETTINGS > PERMALINKS and hit save. This will re-generate your .htaccess file. Happy days now!!!

WE CAN FIX THIS ISSUE FOR YOU RIGHT NOW

#4 RULE OUT WORDPRESS CORE AS AN ISSUE

Sometimes for many different reasons, your core WordPress installation may have an issue. This could be files missing, changed or corrupted. You want to make sure that your core WordPress installation is fresh and new to rule out this being the cause of your server WordPress 500 Internal Server Error. Take a look below to see how you can manually remove and re-install WordPress core files.

  1. Get the latest WordPress zip (or tar.gz) file.
  2. Unpack the zip file that you downloaded.
  3. Deactivate plugins.
  4. Delete the old wp-includes and wp-admin directories on your web host (through your FTP or shell access).
  5. Using FTP or your shell access, upload the new wp-includes and wp-admin directories to your web host, in place of the previously deleted directories.
  6. Upload the individual files from the new wp-content folder to your existing wp-content folder, overwriting existing files. Do NOT delete your existing wp-content folder. Do NOT delete any files or folders in your existing wp-content directory (except for the one being overwritten by new files).
  7. Upload all new loose files from the root directory of the new version to your existing wordpress root directory.

NOTE – you should replace all the old WordPress files with the new ones in the wp-includes and wp-admin directories and sub-directories, and in the root directory (such as index.php, wp-login.php and so on). Don’t worry – your wp-config.php will be safe.

Be careful when you come to copying the wp-content directory. You should make sure that you only copy the files from inside this directory, rather than replacing your entire wp-content directory. This is where your themes and plugins live, so you will want to keep them. If you have customized the default or classic themes without renaming them, make sure not to overwrite those files, otherwise you will lose your changes. (Though you might want to compare them for new features or fixes..)

Lastly you should take a look at the wp-config-sample.php file, to see if any new settings have been introduced that you might want to add to your own wp-config.php.


#5 CHECK YOUR PLUGINS OR ACTIVE THEME

Now if all the above does not isolate the cause of your WordPress 500 internal server error, you can check to see if it is a plugin or your active theme making this hair pulling issue happen. For this you will need either FTP access or access to your web hosting control panel file manager area. What we will do here is navigate to our plugins folder which will have a path of WP-CONTENT > PLUGINS. All you need to do now is rename the PLUGINS folder to something like PLUGINS_OFF. Now try to reload your site. If it loads up with an error, you know for sure it is a plugin. Login and visit your plugins page. Doing this will turn them all off. Now go back and revert the folder name back to its original folder name PLUGINS. Now go reload the plugins page inside your admin area and turn them on 1 at a time until you find the one that causes the WordPress 500 internal server error.

If the WordPress 500 internal server error is being caused by your active theme, we can know this for certain by navigating to your themes folder which will have a path of WP-CONTENT > THEMES. Now rename the THEMES folder to something like THEMES_OFF. Reload the site and if it loads, you know 100% that the theme is the issue.

We really hope this was helpful if isolating the cause of your WordPress 500 internal server error. If you are stuck or have any questions about any of this, please comment below.

8 Shares
WordPress Speed Up Service

You May Also Like…

12 Comments

  1. Mofakharul

    Very informative indeed.

    I have got the same Internal Server Error, HTTP error 500 after having an attempt to duplicate the site from one location to another using the plugin ‘Duplicator (Free Version)’. I have checked and found okay up to the Step # 4 as you mentioned here but not able to fix it yet. I am a bit confused about the Step # 5. Should I need to install the WordPress in my localhost and then copy the directories & files as you mentioned? Or, straight away from the unzipped folder? Here at Sl. No. 3 you instructed to deactivate ‘plugins’. How to make this deactivation when my site is not running at all and wp-admins is not working and I am not in a position to get entry into my WP dashboard?

    Reply
      • unckl_K

        Why can you not just answer the question? “No. 3 you instructed to deactivate ‘plugins’. How to make this deactivation when my site is not running at all and wp-admins is not working and I am not in a position to get entry into my WP dashboard?”

        Reply
        • WP Fix It Support

          Not sure what you are talking about. There is no mention at all in this entire article about using your admin area to fix the issue. The admin area is not accessible in this case. You must troubleshoot using FTP or web hosting control panel access as explained in detail above.

          Reply
  2. Bob Kruse

    This error is such a pain! I have a lot of sites and every now and then for the last few months, I’ll find that one of them is suddenly giving me this error. All I have to do to fix it is delete my htaccess file, but… it’s still super annoying!

    Reply
  3. Abdulrahman

    I followed the steps mentioned here but I started from the plugins which were causing the problem. I suggest disabling the plugin files before replacing WP files. Anyways this was a life and time saver. Thank you very much!

    Reply
  4. Pieter

    In my case, I found it very peculiar!

    I think my sites were hacked or something like every day a certain time it breaks! !

    I restore and all is well until the next day!

    I did the .htaccess procedure will check tomorrow and also increase add a memory setting in the wp-config file. So will check tomorrow.

    I think I may need to the replace Wp-incldue / admin directories at the end of the day !

    Thanks
    P.

    Reply
  5. harsh

    I have Tried All the Points still I haven’t Got the solution,
    I have renamed the .htaccess file, plugin folder, gave permission 755 to 777, increased memory limit in the wp-config file but the site is still showing error. below is the screenshot.
    https://www.screencast.com/t/yeHpywRaLoMJ

    Reply
  6. Joni

    I had this problem when moving two sites to new hosts. It was just when I had copied the files over – the main page showed but any of the sub-pages didn’t (using the temporary url my host gave me). But as soon as the nameservers were updated and the domain moved as well, it worked fine.

    Reply

Submit a Comment

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

LET US GET STARTED RIGHT AWAY

READY TO GET YOUR SITE FIXED