Diagnostics Center
Diagnostics Center collects account-scoped HTTP, PHP, database, application, and log evidence for one hosted domain, giving support a useful first picture without unrestricted shell access.
Where to find it: Open the account and choose Diagnostics Center.
Available to: The account user for their own account, plus root or the owning reseller when working inside that account. The item may be hidden when its feature profile or required service is disabled.
What this page does
Use it when a site is unavailable, slow, returning an error, or behaving differently after a change. The page correlates supported checks in the selected account and domain scope; it is an investigation view, not an automatic repair button.
Before you start
Select the exact account and domain, record the customer symptom and time, and reproduce the request safely if possible. A healthy summary can coexist with an application-specific bug, so preserve the original error and relevant request context.
Diagnostic areas
| Area | What it helps answer |
|---|---|
| HTTP | Does the selected domain resolve and return a useful status, redirect, or upstream error? |
| PHP | Is the selected PHP runtime, pool, or relevant configuration consistent with the domain? |
| Database | Is the supported database service available, and is there evidence of pressure or connectivity trouble? |
| Application | Can SHM identify supported application and runtime context for the domain? |
| Logs | Do bounded recent entries explain the time and symptom under investigation? |
UI diagnosis versus assisted repair
The Diagnostics Center UI reads and presents evidence. Supported API and AI workflows can also provide bounded code search, runtime summaries, fix plans, repair runs, and rollback operations when authorized, but those are separate, explicit actions. Reading a diagnosis never silently edits the customer's site.
Bounded code search
When used through the supported account diagnostics API or AI catalog, Code Search runs inside the account identity and allowed paths, applies time and result limits, excludes private or noisy areas by default, and redacts short previews where required. It is a search aid, not permission to read arbitrary server files.
How to use it
- Select the affected domain and run or refresh the diagnostics.
- Start with the first failing layer: HTTP, runtime, database, application, or logs.
- Correlate the result with Health Center, Resource Usage, Access Log, Error Log, or service Status.
- Build the smallest repair in the module that owns the failing state.
- Repeat the original customer request and refresh diagnostics.
Result and next check
You should finish with a bounded finding or a clear next diagnostic step. After a repair, the original request must work and the related diagnostic evidence should no longer show the same failure.
Theme color