A useful support ticket tells us which server, which site, what went wrong, and when it started. With those four facts we can search logs on the first reply. “Site down please help” is understandable, but it sends us looking for a hostname you already have on the invoice.
What to put in the first message
- The domain (example.com) and the server hostname if you have it.
- The exact error — a status code, a PHP fatal, a bounce message, or the panel text.
- When it started. Host clocks here are UTC, so a UTC time is ideal.
- Whether you can still reproduce it.
- What you changed in the last hour (a plugin, DNS, PHP version, a restore).
A subject that works looks like: LiteSpeed 503 on /checkout, example.com, since 14:10 UTC. Attach a log instead of pasting four thousand lines. If you paste, quote about twenty lines around the first error. A screen recording of you clicking is harder to search than those twenty lines.
date -u; hostname; curl -sI https://example.com | headdate -u is the clock we will search. hostname is the machine, which is not always the domain. The curl headers are what the site actually returned, not what a plugin’s health page claimed. Paste that block; it replaces a paragraph of guesswork.
One ticket per problem
If you already opened a ticket for the same 503, reply there. A new ticket loses the log paste and the person who already looked. If a second problem showed up, say so on the same thread: “mail is bouncing now too.” If you are still editing the site while we look, say that — otherwise we chase a plugin you just disabled.
Preview a migrated site before you ask us to switch DNS. Preview a migrated site before switching DNS is the runbook for that.
Tagged
Was this article helpful?
Be the first to rate this article.
