StarDomain

Plesk Services Not Starting Troubleshooting Guide

Plesk Services Not Starting Troubleshooting Guide

When Plesk services fail to start, your website, email, or database may become unavailable.

Key Services

ServicePurposeImpact If Down
IISWeb serverWebsites not loading
MySQL/MSSQLDatabaseDatabase-driven apps fail
Mail ServerEmailEmail stops
FTP ServerFile transferCannot upload via FTP
Plesk ServiceControl panelCannot access Plesk

Checking Service Status

Via Plesk

Tools & Settings > Service Management. Green = running, Red = stopped.

Via Client Portal

If Plesk is inaccessible, check service status at {{SUPPORT_URL}}/client and contact support.

Website Not Loading (IIS Issue)

Check:

  1. Application pool status in Websites & Domains > IIS Settings. Try restart.
  2. Recent changes to web.config or PHP settings — revert if needed.
  3. Disk space — clean up if full.

Contact support if: Cannot restart app pool, pool keeps crashing, Plesk inaccessible.

Database Not Connecting

Check:

  1. Verify credentials in application config
  2. Check disk space
  3. Test via Plesk > Databases > phpMyAdmin

Contact support if: Database management tools also fail, service shows stopped.

Email Not Working

Check:

  1. Verify email client settings
  2. Test webmail through Plesk
  3. Check MX records
  4. Check mailbox quota

Contact support if: Webmail also fails, mail service stopped.

FTP Cannot Connect

Check:

  1. Verify credentials, port (21 FTP, 22 SFTP)
  2. Check firewall, try passive mode
  3. Check for IP block (wait 15-30 min or contact support)

Plesk Panel Inaccessible

Check:

  1. URL correct: https://server-ip:8443
  2. Try different browser/incognito
  3. Try different network
  4. Ping the server

What {{COMPANY_NAME}} Support Can Do

  • Restart services (IIS, MySQL, mail, DNS, FTP)
  • Check server health (CPU, memory, disk, network)
  • Review server-level logs
  • Fix server configuration issues
  • Restore from server-level backups

When contacting support, provide: Domain name, what is not working, when it started, recent changes, error messages/screenshots.

Preventive Measures

  • Regularly check disk space and clean up
  • Keep applications and PHP updated
  • Test immediately after configuration changes
  • Keep backups of config files before modifications

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