Answer:
This article explains the common reasons why your website may display a “500 Internal Server Error” and how to troubleshoot the issue on GHFS Hosting using Plesk.
1. What Is a 500 Internal Server Error?
A 500 error indicates that something went wrong on the server, but the exact cause is not immediately visible.
It generally means the website’s code, configuration, or permissions are causing the server to fail while processing the request.
2. Common Causes of 500 Errors
2.1. Incorrect File or Folder Permissions
If permissions are set too high or too low, the server may block access.
Typical recommended permissions:
-
Folders: 755
-
Files: 644
2.2. Errors in .htaccess
A misconfigured or unsupported rule in .htaccess can cause an immediate 500 error.
Examples include:
-
Wrong rewrite rules
-
Syntax errors
-
Unsupported modules
2.3. PHP Errors
Your website’s PHP script may be causing the error due to:
-
Deprecated functions
-
Fatal errors in code
-
Unsupported PHP version
-
Missing PHP modules
2.4. Reaching Resource Limits
If your hosting plan's limits are exceeded (CPU, RAM, I/O), the server may return a 500 error.
2.5. Corrupted or Missing Files
Incorrect uploads, incomplete transfers, or corrupted configuration files may prevent the site from loading.
3. How to Diagnose the Error in Plesk
Step 1: Check Error Logs
-
Log in to Plesk
-
Go to “Websites & Domains”
-
Select the domain
-
Click “Logs”
Look for error messages labelled as error, fatal, or php-fpm, which usually point to the root cause.
Step 2: Review File Permissions
-
Open “File Manager”
-
Check folder permissions
-
Adjust to 755 for folders and 644 for files if necessary
Step 3: Examine the .htaccess File
-
Locate the .htaccess file in your site’s root directory
-
Temporarily rename it (for example: .htaccess_backup)
-
Reload your site
If the site loads, the .htaccess file contains the problem.
Step 4: Check PHP Version and Settings
-
Go to “PHP Settings” in Plesk
-
Try switching to a stable version of PHP
-
Ensure required PHP extensions are enabled
Step 5: Re-upload Missing or Corrupted Files
If the error started after an upload or update, try re-uploading files.
4. When to Contact GHFS Hosting Support
Contact support if:
-
You cannot identify the error in the logs
-
Your website is still showing 500 after checking the common causes
-
You need help with diagnosing PHP or configuration errors
-
You suspect a server-level issue
GHFS Hosting support can review logs, restore backups, and help fix underlying issues.