internal server error

Dealing with Internal Server Error

Information on Dealing with Internal Server Error by Pinguis Web Design

Generally the first response and the natural one is to freak out (after 10’s or 100’s of hours work).

Don’t rush off deleting. Backup your database if any create a copy of your files then when you have got past the initial freak out…

Action is required.

The 500 Internal Server Error is a general error status code that means something has gone wrong on the web site’s server, but the server could not be more specific on what the exact problem could be and how to solve internal 500 errors.

On WordPress website 500 errors are usually .htaccess file error. Sites get hacked or the .htaccess file can get rewritten, servers get overloaded or website are badly hosted(personally i recommend blacknight hosting in Ireland). If you have access to your server through ftp go to deleting the file and re-saving your permalinks will recreate your .htaccess file. Of course read/write permissions are necessary but If WordPress cannot create/edit your .htaccess, there will be instructions at the bottom of the page. Basically in your text editor create an file name it .htaccess and paste the following content into the file, upload it and refresh your browser(additional browser steps below)

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]


# END WordPress

 

Most of the time, a 500 Internal Server Error displays inside the Internet browser window, just as web pages do.

What may cause the 500 Errors

As I mentioned above, Internal Server Error messages indicate that something, in general, is wrong.

Wrong can means an issue with the page or site’s programming, but there’s certainly a chance the problem is on your end, something we’ll investigate below.

 

How To Fix the 500 Internal Server Error

A 500 Internal Server Error is a server-side error, meaning the problem probably isn’t with your computer or Internet connection but instead is a problem with the website’s server.

Additional browser steps below…

  1. Reload the web page. You can do that by clicking the refresh/reload button, pressing F5, or trying the URL again from the address bar.Even if the 500 Internal Server Error is a problem on the web server, the issue may only be temporary. Server maybe overloaded. Trying the page again will often be successful.
  2. Clearing your browser’s cache. If there’s a problem with the cached version of the page you’re viewing, it could be causing HTTP 500 issues.Note: Internal Server Errors are not often caused by caching issues, but I have, on occasion, seen the error go away after clearing the cache. It’s such an easy and harmless thing to try so don’t skip it.
  3. Browser’s cookies. Some 500 Internal Server Error issues can be corrected by deleting the cookies associated with the site you’re getting the error on.After removing the cookie(s), restart the browser and try again.
  4. Troubleshoot as a 504 Gateway Timeout error instead.It’s not very common, but some servers produce a 500 Internal Server Error when in reality a more appropriate message based on the cause of the problem is 504 Gateway Timeout.
internal server error
How to deal with internal server error website not appearing or Website is Blank

 

Fixing a 500 Internal Server Error Problems on Your Own Website.

500 Internal Server Error on your own website requires a completely different course of action. As I mentioned above, most 500 errors are server-side errors, meaning it’s likely your problem to fix if it’s your website.

There are lots of reasons why your site might be serving a 500 Error to your users, most common reasons are:

  • File Permissions Error. In most cases, a 500 Internal Server Error is due to an incorrect permission on one or more files or folders. In most of those cases, an incorrect permission on a PHP and CGI script is to blame. These should usually be set at 0775 (-rwxr-xr-x).
  • PHP Timeout. If your script connects to external resources and those resources timeout, an HTTP 500 error can occur. Timeout rules, or better error handling in your script, should help if this is the cause of the 500 error.
  • Coding Error in .htaccess. Common error, check that your site’s .htaccess file is properly structured and with running proper permissions.

If you’re running WordPress, Joomla, or another content management or CMS system, be sure to rename(place a 1 in front) or delete your .htaccess, make sure that you go to Settings and Permalinks and click the save button. This will generate a new .htaccess file for you with proper rewrite rules to ensure that your post/pages do not return a 404. Reload your website and check results if necessary contact your  hosts support center.