# Troubleshooting

| Symptom | Likely cause | Self-service action |
|---|---|---|
| "Account is suspended" | Operator suspended your account | Contact your administrator |
| The panel shows "The control panel is temporarily unavailable" | The panel of this server cannot be used right now (an issue on the hosting side) | Nothing to do on your side — your websites, mail and other services keep running. Use **Try again** later or contact your hosting administrator; **Sign Out** ends your session |
| Cannot log in, password definitely correct | 2FA enabled but device lost | Use a backup code; if none left, contact administrator |
| Mail not arriving (sent from your account never reaches recipient) | DKIM / SPF not published in DNS | DNS page — check that the zone has one SPF record, the DMARC record and the `default._domainkey` DKIM record (the server writes them while your account's mail DNS is on; if they are missing, ask your hosting administrator). If your DNS is hosted elsewhere, copy them to that provider |
| Mail "Connection refused" from your client | Port `587`/`993` blocked by firewall or ISP | For sending, try port `465` (SMTPS — SMTP over SSL; it is not an IMAP port); some ISPs block port `25` outbound |
| Site returns `500 Internal Server Error` | PHP fatal error | Open `/home/{user}/logs/php-error.log` from the File Manager |
| Site returns `502 Bad Gateway` | Per-account Python / Node app crashed | App detail page → Logs → restart |
| Let's Encrypt issuance failed | DNS not yet propagated to Let's Encrypt | Wait 5–10 min and retry; verify the domain's A record points to the server IP |
| "Quota exceeded" creating a new resource | Disk full | File Manager → the **Disk Usage** bar shows how much of your quota is used; download and delete files you no longer need. Files under `logs/` cannot be deleted (the server rotates them daily and keeps 14 days); mailboxes are stored outside your home directory and do not count here |
| Database error: "Too many connections" | Application not releasing connections | Review the application's database connection settings (close connections, lower its pool size); the panel has no pool restart — if the error persists, contact your hosting administrator |
| FTP error: `530 Login incorrect` | Username format wrong | Use the full name shown on the FTP page — `{user}_{name}` (the FTP user created with your account is `{user}_{user}`); if it still fails, set a new password with the row's **Change Password** action |
| Cron job runs but produces no output / no email | Output goes to the server-side mailbox | Add `>> /home/{user}/cron.log 2>&1` to the command (the `logs/` directory is not writable by jobs) |
| Backup restore overwrote a config | Restored from the wrong backup | Backups page → Restore from a previous archive (older backups are kept up to retention) |
| 2FA backup codes lost | All codes used or misplaced | Settings → Security → Generate new set (invalidates old codes); requires current authenticator working |
| Panel paints a few seconds late right after several sign-ins from your address | The server rate-limits sign-in calls per address and answered `429` to the session check | Nothing — the panel waits and asks again; you are signed out only when the session really ended |

When the issue is outside your control (operator action, DNS propagation, mail relay limits), contact your hosting administrator. **Include the timestamp shown in your notification or browser** — it speeds up correlation in their audit log.

---