Many website problems on Plesk have standard fixes: wrong file permissions after an upload, a crashed database table, a stuck service. The free Repair Kit extension gives customers safe buttons for these fixes, and administrators have the more powerful plesk repair utility.
Before you start
- Administrators: install Repair Kit from Extensions → Extensions Catalog and make it available to customers.
- A recent backup before running repairs on important sites.
Customers: open Repair Kit
Go to Websites & Domains, open the domain and click Repair Kit (it may be under the domain's More menu or the dashboard). The page lists checks and fixes for your subscription.
Typical fixes
| Problem | Repair Kit action |
|---|---|
| 403 errors or "permission denied" after uploading files | Fix file permissions for the website |
| "Table is marked as crashed" database errors | Check and repair databases |
| Site down after a change, PHP-FPM stuck | Restart the site's web services (where allowed) |
| Website not resolving | Check DNS to see if the domain points to the server |
Each action explains what it changes before you confirm. Run one fix at a time and test the site after each.
Administrators: plesk repair
Over SSH as root, the plesk repair utility checks and fixes much more:
plesk repair all -n– check everything and report problems without changing anything.plesk repair fs example.com– fix ownership and permissions of one domain's files.plesk repair web example.com– regenerate web server configuration for a domain.plesk repair db– check and repair Plesk's own database.plesk repair mail– fix mail server configuration and mailbox permissions.
Always run with -n first to see what would change, then run without it to apply fixes.
When repairs do not help
- Read the error in the Log Browser – application errors (a plugin bug) are not fixed by permission repairs.
- Follow the site not loading checklist.
- Restore from backup if files were damaged or infected.
- Contact support with what you tried and the error message; MdmHost customers can open a ticket.
Troubleshooting
- Repair Kit not visible: not installed or not enabled for customers.
- Permissions break again: a deployment script or FTP client sets wrong permissions; fix the tool's settings.
- Database repair fails: severe corruption; restore the database from backup.