Fix 500 Internal Server Error on GARMTECH Hosting

A 500 Internal Server Error means the server could not process the request. On shared hosting this is most commonly caused by a website-level issue: a PHP fatal error, a broken .htaccess rule, wrong file permissions, or a temporary resource limit.

This checklist is written for GARMTECH Web Hosting (Plesk) and focuses on actions you can do yourself in Plesk.

Before you start

• Open the website in an incognito/private window (to avoid cached redirects and cookies).
• Check if the error happens on all pages or only on one URL (for example /wp-admin).
• If you manage multiple domains in the same Plesk subscription, check whether only one domain is affected.

1) Check the website error log in Plesk

1. Log in to Plesk from My.GARMTECH (open your hosting service and click Login to Plesk).
2. Go to Websites & Domains → select the affected domain.
3. Open Logs and look for entries in error_log around the time you saw the 500 error.

What to look for: messages like “PHP Fatal error”, “Allowed memory size exhausted”, “Premature end of script headers”, or “RewriteRule: bad flag”.

2) Fix a broken .htaccess (very common)

If the problem started after adding redirects, security rules, or a plugin update, a syntax error in .htaccess can cause 500.

1. In Plesk, open Files (File Manager).
2. Open httpdocs (this is the default document root for most websites).
3. Find .htaccess and rename it to .htaccess.bak.
4. Reload the website.

If the error disappears, the issue is inside the old .htaccess. Restore it and correct the last changes (or recreate a clean file for your application).

3) If it is WordPress: disable plugins/themes and test

Many 500 errors on WordPress happen after installing/updating a plugin, theme, or switching the PHP version.

Option A: Disable plugins in WordPress Toolkit (if you can access it)

1. Plesk → WordPress (WordPress Toolkit).
2. Open your site.
3. Disable plugins one by one (start with security/caching plugins) and re-test the website.

Option B: Disable plugins via File Manager / FTP-SSL (if wp-admin is not accessible)

1. Open httpdocs → wp-content.
2. Rename the folder plugins to plugins.disabled.
3. Reload the website. If it works, restore the folder name and disable plugins one by one (rename a plugin folder) to find the culprit.

Note: On GARMTECH hosting, file upload is supported via FTP-SSL (FTPS). For a valid SSL certificate during FTP connection, use your server hostname as the host in your FTP client.

4) Check PHP version and PHP limits

500 errors are often caused by incompatible PHP versions or insufficient memory/time limits.

1. Plesk → Websites & Domains → your domain → PHP Settings.
2. Try switching to a stable PHP version (if available in your plan).
3. If the error log shows “Allowed memory size exhausted”, increase memory_limit (and, if needed, max_execution_time and max_input_vars).

5) Check disk space (quota) and temporary folders

If your hosting disk quota is full, websites may fail to write sessions/cache/uploads and return 500.

• In Plesk, check Statistics or Disk usage for your subscription.
• Clean up old backups, unused files, and large log archives.

6) Roll back changes (restore from a backup)

If the error started “suddenly” after an update, a restore is often the fastest safe fix.

• Plesk → Backup Manager → restore the latest working backup.
• If you only changed one component (for example, a plugin), consider restoring only files or only the database (advanced).

What to collect if you need to escalate

If none of the steps above helps, prepare these details (they save time):

• The exact URL that shows 500 (home page, admin page, specific script).
• The time when it happened (with your time zone).
• 3–10 lines from error_log around that time.
• What changed right before the issue (plugin/theme update, new redirect rule, migration, etc.).