Knowledgebase: How to Fix a 500 Internal Server Error
A 500 Internal Server Error means something went wrong on the server. Itβs not specific, but it often relates to issues in your .htaccess file, incorrect file uploads, or plugin/theme conflicts (in WordPress).
Follow the relevant steps below depending on whether your site is a static HTML or a WordPress installation.
π Static HTML Sites
1. β
Check for a Valid index.html
Your homepage must be named index.html
(or index.php
, if needed) and must be placed in the root folder of your File Manager.
-
Make sure your files aren’t buried in a subfolder.
-
index.html
should be directly inside/public_html/
(or root folder).
If the server can’t find this file, it may return a 500 or 403 error.
2. β οΈ Fix .htaccess Errors
A bad .htaccess
file is one of the most common causes of 500 errors on static sites.
Fix:
-
Go to File Manager in your PBN LTD dashboard.
-
Find
.htaccess
in the root folder. -
Rename it to
.htaccess-backup
to disable it. -
Create a new
.htaccess
file and paste in this clean version:
# Use index.html as the default file
DirectoryIndex index.html
# Prevent directory listings
Options -Indexes
# Enable rewrite engine (optional, only if you're using rewrites)
<IfModule mod_rewrite.c>
RewriteEngine On
</IfModule>
-
Save and refresh your website.
β
If your site now works, your previous .htaccess
file had invalid or unsupported rules. You can now go back and review your old code, re-adding only what’s necessary one step at a time, or correcting the errors before re-uploading.
3. π Reupload Your Files
A 500 error can occur if files were uploaded partially or became corrupted during transfer.
-
Reupload your full site using File Manager.
-
We recommend uploading your site as a
.zip
file and extracting it inside the dashboard for best results.
βοΈ WordPress Sites
1. β οΈ Corrupt .htaccess File
WordPress uses a more complex .htaccess
structure. This file is automatically generated, but errors or manual edits can break your site.
Fix:
-
Open File Manager and rename the
.htaccess
file to.htaccess-backup
. -
Refresh your site. If it works now, the problem was in that file.
-
Create a new
.htaccess
file with this standard WordPress code:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
2. β Plugin or Theme Conflicts
If the 500 error occurred after installing or updating a plugin or theme, it's likely a PHP issue.
Fix:
-
Open File Manager and go to:
-
/wp-content/plugins/
-
/wp-content/themes/
</li> <li data-end="3188" data-start="3092"> <p data-end="3188" data-start="3094">Rename the most recently added or edited folder (e.g. <code data-end="3161" data-start="3148">plugin-name</code> → <code data-end="3186" data-start="3164">plugin-name-disabled</code>).</p> </li> <li data-end="3208" data-start="3189"> <p data-end="3208" data-start="3191">Refresh the site.</p> </li>
-
β If your site works, the problem was with that plugin or theme.
3. π§± Corrupted Core Files or Uploads
Manually migrated or partially uploaded WordPress files can result in errors.
Fix:
-
Reupload WordPress core files, or restore a backup from your PBN LTD dashboard.
-
Always use the official version of WordPress files and upload via File Manager.
4. π Permissions Issues (Rare)
Incorrect permissions can sometimes trigger a 500 error.
-
Files should usually be set to
644
, folders to755
. -
You can check and adjust these by right-clicking files in File Manager.
π§π» Still Seeing the Error?
If none of the steps above resolve the issue:
-
Double-check that the correct default file (
index.html
orindex.php
) exists in your root folder. -
Clear your browser cache and try again.
-
Restore a backup from your dashboard if available.
π© Need More Help?
Submit a support ticket and include:
-
The domain name
-
When the issue started
-
What changes were made recently
-
Any relevant screenshots or error messages
Clear details help our team assist you faster!
View other On-Site Issues articles, or continue viewing other knowledgebase articles.