Error case - HTTP Error 500 Internal Server Error

Main Issues responsible for 500 Internal Server Error

The 500 Internal Server Error is a very general HTTP 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 is. Since the issue is server-based, the resolution needs to be server-related.

Prerequisites

• Access to cPanel or

• Access to Funio Hub

Task completion: 15 minutes

Expertise: Intermediate

Case 1 : Misconfigured .htaccess file

A .htaccess is a directory-level file that is used primarily for directory management, such as securing folders, redirections, customized error responses, etc. When the 500 error is caused by this file, it means it is trying to perform a server task that is not working out very well. To check if this file is the source of the issue:

1. Log onto the server through FTP (or with cPanel File Manager).

2. Look for the .htaccess file in the /public_html/ directory

3. Rename the .htaccess file to old.htaccess

4. Look at your site!

When you do this, it might not do the redirection or take into account other factors that the .htaccess was performing. But are you still receiving the 500 error? If so, check for the other case scenarios. If not, review your .htaccess file for misconfigurations.

Case 2 : File / Folder permissions

If you just uploaded a new file or folder to your account that is being called by the URL you are trying to access, that is surely the situation you are encountering. It might be a module you just downloaded and added to your CMS that has "wrong" permissions. Oftentimes, these files might have 777 permissions, which means that the Owner/User/Group has full permission to do what they please with the file/folder because 7 is the highest level. 7 means: Execute, Read and Write.

Permissions for folders should be: 755
Permissions for files should be: 644

Fixing the issue

1. Log onto the server through FTP (or with Panelbox File Manager)

2. Find the file(s) you just uploaded and right-click on it(them).

3. Change the numbers to 755 for a folder or 644 for a file

Doing this through an FTP client is recommended if you have multiple files/folders to modify. It will allow you to change recursively the folder permissions to sub-folders, and the same for all the files at the same time. This means you would save some time and hardship.

Case 3: If the site loads slowly and you receive this error intermittently

• This might have been a temporary issue caused by conflicting sessions on your website. You can clear the active sessions from your browser history if you need to.

• This might be that your website is using a lot of server resources and it is being "throttled" down by the server to use fewer resources. The website requests would be timing out and conflicting sessions would appear because of this, causing the 500 error you see. Consequently, you would check the following:

  • Check the Error Logs for any trace of the 500 error and its source (Under cPanel > Stats > Error Log).

  • Check the resource usage in cPanel (on the right-hand side of the main page).

We hope this puts you on the right track to solve the 500 internal server errors!

Related Articles

Log in to your cPanel