Español
Deutsch
A 500 error is intentionally vague — it just means something went wrong on the server, without specifying what. Here's how to narrow it down.
Check Your Error Logs First
Plesk's error log, found under Logs in your domain's settings, usually contains a far more specific error message than the generic page visitors see.
Recently Changed Something?
A newly installed plugin, a theme update, or a manually edited configuration file are the most common triggers. Reverting the most recent change is often the fastest fix.
Check File Permissions
Incorrect permissions on files or folders (especially after a manual upload or migration) can trigger a 500 error. Standard permissions are 644 for files and 755 for folders.
Check .htaccess for Errors
A malformed .htaccess file is a frequent culprit on Apache-based hosting. Temporarily renaming it to confirm whether it's the cause is a quick diagnostic step.
PHP Memory or Timeout Limits
A script that runs out of memory or takes too long can trigger a 500 error — increasing PHP's memory limit through Plesk sometimes resolves it if this is the cause.
Still Stuck?
Share the specific error log entry with our support team — it turns a vague guessing game into a fast, targeted fix.
