Search results for:
Table of Contents
This error usually will look something like this:
The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, email@example.com, and inform them of the time the error occurred. Anything you might have done may have caused the error. More information about this error may be available in the server error log.
If you see a 500 Internal Server Error, the server wasn't able to fulfill a request that appeared to be valid. Any error code that starts with the number five (5) means the server knows it's come across a problem and cannot do what's requested.
A general 500 Internal Server Error is probably caused by a simple mistake in the configuration somewhere on your site or a script that you're using. It doesn't tell you precisely what the issue is, as it's a general error. (We'll briefly explain other specific errors that start with five (5) at the bottom of this page)
Causes may include, but aren't limited to:
To find the exact cause, you should look at the error logs found in cPanel. If you need help, get in touch, and one of our techs will be happy to help you figure it out.
To fix a 500 Internal Server Error, there are several possible causes to investigate. First, make sure the .htaccess file is correct, then make sure the folders and files on your site have the correct permissions, check for any problems with themes and plugins, and check PHP code for errors.
The solution depends on what initially caused the error. Once you've identified the cause, then you can try to fix it. Here are some of the more common causes and what you can do to try to fix them…
This is probably the most common cause of a 500 error. If you aren't sure, follow these steps to determine if it's the cause (if you couldn't find the reason in the error logs):
If the error is gone, then it's a problem with your .htaccess file. Change it back to the original name and start snipping out pieces of the code within the .htaccess file to identify which line is the problem. To do this quickly and safely, just put a number sign (#) without the parenthesis at the start of one line.
This will "comment out" that line, so it's not "read" when your site is loaded.
Do one line, then check to see if the error persists. If it does, add it to the following line and check again. Once you've found the problem line and fixed or removed it, remember to uncomment all the other lines.
If you check all the lines and the problem persists, move on to the next section.
Files and folders should have specific permissions set for them. You can see what they're set to and change them by going to the File Manager in your cPanel and look for "Permissions."
The permissions should be:
Folders – 0755
Files - 0644
If nothing here solves the problem, please contact us on live chat or submit a ticket to help you get it sorted and your site back online.
Sometimes a 500 error can be caused by a plugin or theme.
If the error shows up after you've installed a new plugin:
If the error shows after you've installed a new theme:
If that fixes the site, try reinstalling the theme or plugin. If it throws the error again, change the name and leave it.
Issues with PHP can also cause a 500 error. Make sure you have PHP error reporting turned on so you can look and see there's a possible problem. You can turn it on by doing the following:
display_error = off log_errors = On error_log = “error.log”
If your PHP code initiates external connections (Grabbing an RSS feed, etc.), make sure you include a time-out handler. If a PHP script times out in a clunky way, it can throw a 500 error.
Also, make sure PHP applications have enough memory allocated to them. If it's too low, it will cause a fatal error.
The server cannot fulfill the request, or it simply doesn't understand what it's requesting. The request method may not be valid, or the server may not support the request method. In some cases, there may be software on the server that needs to be updated. This is often when something isn't available yet, like new features being added to an API.
The server received a request from another server that's not valid. It may be displayed in various ways, including:
You'll also often see "nginx" on the screen.
These errors are often just a quirky problem between servers online that you don't have any control over. Other times it may be something you can thank your browser for. If you see this error, try clearing your cache, checking your internet connection, and checking if the site works in another browser or from another connection. If it persists, please get in touch with us!
This error is similar to the 502 one, but instead of not fulfilling the request, it simply isn't getting a request. This may be a problem with the server, or you may be running scripts that require more time to run entirely.
First, refresh the page to see if it persists. If it does, you can try to fix this:
The server doesn't support the HTTP protocol being used in the request it's sent to. Try using a different browser and see if it works, as it could be a problem with an outdated browser.
You could see several other errors like these. The cause and solution will be dependent on where you see this. For example, are you seeing the error on a WordPress site or one of our cloud/dedicated servers? If you happen to see any odd errors like this, please contact us to get a tech on it and help you get it resolved.
Written by Michael Brower / December 13, 2016