Troubleshooting
Each page starts from what you see, lists the causes from most to least likely, and gives a check for each. The guides in Guides hold the procedures these pages point to.
| You see | Page |
|---|---|
| The panel address shows “Hyperion is updating”, “The update didn’t finish” or “The control panel isn’t answering”, refuses the connection or warns about its certificate | The panel does not load or says it is updating |
| “Incorrect username or password”, “This account is locked”, “Too many failed attempts from this address” or a code that does not match | Cannot sign in to the panel |
| A website shows “This site is temporarily unavailable.”, 502, 503, 504, or 403 and 404 on every page | A website shows an error page |
| “Certificate issuance failed”, “DNS pre-check failed” or a browser certificate warning | A certificate request fails |
| “node … unreachable”, “response failed authentication” or “envelope too old” | A node shows as unreachable or its answers are rejected |
A backup in the state failed, “not enough disk space”, an off-site copy that is not confirmed |
A backup fails |
| A site’s mail is not delivered, or “message file too big” | Mail from a website is not delivered |
| WordPress shows a critical error or a white page | WordPress shows a critical error |
/api/v1 answers 400, 401, 403, 404, 409 or 429 |
An API request is rejected |
An update that stops partway is covered in Recover from a failed update. Moving or importing a site that fails is covered at the end of Move or copy a site and Import sites with one command. A failed slow action has its cause in its log: see Follow background jobs.