WordPress “Internal Server Error” (500) – How To Get It Working Again
If WordPress experiences a “deadly” error, it will display the “Internal Server Error” page – a black + white page which will clarify some different points/information.
The page has nothing to do with WordPress; it’s raised by the web server software (typically Apache) as a way to show 500 errors.
HTTP errors occur on the Internet ‘all’ the time – the most widely recognized is the well-known “404” (not found) page. Every one of these errors happens on the browser level, implying that what caused them is commonly reliant on something other than the CMS you’re using.
The fact is that there are two kinds of HTTP error (4xx/5xx), of which server issues cause the “500” error. On account of your WordPress error page, this implies you need to welcome that what you’re seeing is likely the after effect of some more profound issue with either the database, application or HTTP server for your system.
The fix ordinarily requires digging around in the WordPress config files. In this way, if you are not satisfied with anything clarified below, it’s suggested that you discuss with an expert who’ll have the capacity to help deal with it.
Fortunately, the 500/Internal Server Error is caused by a file on your system (not the database).
Try not to worry about your posts/information – they are stored in a database, either on your server or somebody else’s. It’s uncommon for the database to become damaged – it’s, for the most part, the files which do it.
Accordingly, all that you have to do is gone for disposing of damaged/corrupted files that could be prompting the error:
1. Backup Your WordPress Installation Folder
The initial step is to back up the WordPress installation folder, which enables you to keep a “hard copy” of the files which may turn out to be much more corrupted.
To do this, you have to access the “FTP” for your server.
I’m not going to clarify the specifics here – there are excessively numerous different approaches to do it.
The general procedure is to get into the “Control Panel” of your hosting account, use that to access the FTP of your account and download the WordPress installation folder to your device.
The following defines how…
- Log into the “Control Panel” of your hosting account (this will shift contingent upon the host)
- From the control panel, you have two choices – either search for “File Manager” (if using CPanel) or “FTP” (if not using CPanel)
While most hosting companies will utilize CPanel (and along these lines you gain admittance to the inbuilt “File Manager” applet), there are some who don’t have the usefulness.
Because of the idea of the two kinds of system, the backup process changes relying upon which you end up using…
- CPanel (File Manager)
- Click on “File Manager”
- Browse to the folder where WordPress was installed (fundamentally the folder which contains sub-folders including “wp-includes” and so on.)
- Select the folder itself (don’t click into it)
- From the top toolbar, select “Compress”
- This will make a “zip” file of the folder
- Select the zip file and click “Download”
- This should give you the backed-up file
The above is the thing that a lot of people will end up doing. If you’re not using CPanel, you’ll need to use the following suggestions…
- From your hosting account, identify the FTP account information (there are numerous ways this is finished)
- When you have FTP access, you require a way to connect – if you’re using Windows, FileZilla works best
- Use FileZilla to connect to the server
- Select the “WordPress” folder
- Save it to your system
This will let you save the WP folder to your hard drive, enabling you to perform the following activities with an exemption.
Ensure you keep the File Manager /FTP system open.
2. Rename The “Plugins” + “Themes” Folders
As said, the dominant part of reasons for the Internal Server Error/500 Error in WordPress is because of a file being corrupted or damaged.
The prime guilty parties for said damaged files are in the “Plugins” and “Themes” folders – both of which are available to be changed, and both most referred to as the purpose behind the deadly error.
The subsequent step is to rename the “plugins” folder on the server…
- Browse to the wp-content folder inside the main WP folder
- Find the “plugins” folder
- Rename it to “plugins.old” or comparative
- Try to load WordPress once again
If the system doesn’t load, at that point you should repeat the steps with the themes folder.
3. Rename .htaccess
The .htaccess file is used by Apache to decide different routing mechanisms for inbound traffic.
While it frequently works extraordinarily well, there are frequent instances where it will become damaged/corrupted – leading to problems, for example, the one you’re experiencing.
To fix this, you can rename the .htaccess file in your hosting service – which should be possible using the following approaches…
- Click on the “WordPress” installation folder
- Inside, find “.htaccess” and rename it to “.htaccess.bak”
- Try getting to your WordPress admin area in your browser
- If successful, click onto Settings > Permalinks
- Click “Save Changes” (this generates a new .htaccess)
- Verify whether WordPress is working once again
If you follow these steps, it should give you straightforward access to the WordPress admin area again – from which you’ll have the capacity to rebuild the several plugins, and so forth.
If none of the above steps work, it recommends that you have a more extensive issue with the system. An essential thing isn’t to freeze – every one of your posts/settings are stored in the database, implying that regardless of whether you need to complete a total re-install, notwithstanding everything you’ll have them.