Diagnostics Center
Investigate a website problem and review the checks that can help explain it.
Where to find it: Open the account and choose Diagnostics Center.
Available to: The account owner, their reseller or the server administrator. Availability depends on the hosting plan and installed services.
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 limited 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 limited 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
Code Search looks for matching text inside your account’s application files. It limits the results and hides sensitive details where needed. Open the relevant file in File Manager when you need to review it more closely.
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.
Domain, path, scheme, and evidence
Choose the exact domain, request path, and HTTP or HTTPS scheme before Refresh. Diagnostics also exposes a sample-count control. Compare the website probe/topology with the application stack, PHP pool/error state, database activity, and access/error summaries that are available for this account.
Health Center brings together website, PHP, SSL coverage, and mail deliverability checks, with links to the relevant repair/configuration pages. Diagnostics Center is an investigation view, not an automatic repair button. Carry the same selected domain/path into the next page and verify the customer-visible URL after any separate repair.
Result and next check
You should finish with a limited 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