StarDomain

Common Plesk Error Messages and Fixes

Common Plesk Error Messages and Fixes

The most frequently encountered Plesk error messages with step-by-step solutions.

HTTP Errors

403 Forbidden

Causes: No default document (index.html/php/aspx), directory browsing disabled, IP restrictions, file permissions.

Fixes: Upload a default document, check Hosting Settings for default document list, review Web Application Firewall settings, ensure IIS user has Read access.

404 Not Found

Causes: Wrong URL, file deleted or moved, URL rewrite misconfiguration.

Fixes: Verify URL and file existence, restore from backup, check web.config rewrite rules.

500 Internal Server Error

Causes: web.config syntax error, application pool crash, code bug, insufficient permissions.

Fixes: Check web.config XML syntax, restart application pool in Plesk, enable detailed errors to identify the issue, verify file permissions.

503 Service Unavailable

Causes: Application pool stopped, resource limits, maintenance mode.

Fixes: Restart app pool in Plesk, check resource usage, delete app_offline.htm if present.

Enabling Detailed Errors

ASP.NET — Add to web.config:

xml
<system.web><customErrors mode="Off"/></system.web>

IIS — Add to web.config:

xml
<system.webServer><httpErrors errorMode="Detailed"/></system.webServer>

Disable in production after debugging.

Plesk Panel Errors

  • "Unable to connect" — Check server is online, port 8443 accessible, try IP instead of domain
  • "Login failed" — Verify credentials, use "Forgot Password", check IP ban, use SSO from client portal
  • "Subscription limit reached" — Exceeded plan resource limits. Upgrade or remove unused resources.

Email Errors

  • "Mailbox full" — Delete old emails or increase quota
  • "SMTP auth failed" — Check password, enable SMTP auth in client, verify server/port
  • "Not delivering" — Check mail queue, verify MX records, check IP blacklists, configure SPF/DKIM/DMARC

Database Errors

  • "Cannot connect" — Verify database server running, check credentials, test via phpMyAdmin
  • "Access denied" — Wrong credentials or insufficient permissions. Reset password in Plesk Databases.

Need help? Contact our support team at {{SUPPORT_URL}}/client/support.