Panelbotdocs
SearchStart free

AI support for websites down or erroring

How Panelbot diagnoses sites that are down, blank, or throwing 500, 502, or 503 errors, checking whether the site responds and where the failure sits.

Updated

Websites down or showing errors

“My site is down” is the ticket every hosting company knows, and the one with the widest range of causes. The site might be blank, throwing a 500, refusing connections with a 503, or timing out. The customer only sees that it is broken. Panelbot finds out whether the site responds at all, what kind of failure it is, and whether the fault sits with the application, the server’s backend, or plain capacity, then either resolves it or hands your team a clear diagnosis.

What your customers report

Outage tickets tend to sound like this:

  • “My site is down” or “it is not loading at all.”
  • “I get an internal server error” or “a 500 error on the homepage.”
  • “The site shows 502 bad gateway.”
  • “It says 503 service unavailable.”
  • “I get a 504 gateway timeout.”
  • “The page is just blank.”
  • “The site broke right after an update.”

Most customers cannot tell one error code from another, and several of these can appear for the same underlying reason. Panelbot works from the domain and establishes what is actually happening.

How Panelbot looks into it

Panelbot starts with read-only checks that describe the failure without touching anything. It is confirming, in plain terms:

  • Whether the site responds at all, and if so, with what kind of error or whether the page is genuinely blank.
  • What the server itself reports, so an error the visitor sees can be matched to a cause rather than a guess.
  • Whether the problem is the application, the backend, or capacity. A blank page or a 500 usually points at the site’s own code; a 502 or 503 points at the layer that runs the site’s code. Panelbot works out which layer is failing and why before recommending anything, rather than lumping every gateway error together.

These checks are safe to run automatically and give Panelbot the evidence to name the cause instead of offering generic advice.

What it can fix, and what needs your approval

Some outages have a clean, low-risk remedy. When you have enabled action-taking for your account, and the evidence supports it, Panelbot can offer to restart a site’s backend process that has crashed or stopped, bringing the site back online. On WordPress sites, the same diagnosis often leads to reversible fixes covered in the WordPress guide, such as turning off a plugin that is crashing the site or clearing a stuck maintenance flag.

Any such action is presented for confirmation, never taken silently. It is also scoped by impact and by the kind of server involved: on a VPS or dedicated server a backend restart affects only that customer, but on shared hosting the same restart would touch every account on the machine, so Panelbot does not take it unilaterally and escalates to your team instead. With action-taking left off, Panelbot still reports the full diagnosis and describes what would bring the site back, while the change itself stays yours to make.

When a human takes over

Many outages are not safe to auto-resolve, and Panelbot is deliberately conservative. It brings in your team when the evidence points to causes like these:

  • The backend keeps crashing after a restart, which signals a deeper crash loop rather than a one-off stall.
  • The site is failing because the server, or the customer’s account, is out of capacity, where the fix is a limit change or load reduction that belongs to an administrator, not a restart.
  • Neither the site nor the server answers, which is a down service or a firewall issue that needs hands-on work.
  • The cause is a server-wide problem rather than anything scoped to the one account.

When it escalates, the customer sees a clear note that someone on your team is now handling it, and your staff pick up with everything Panelbot has already worked out, so no one starts cold. Outages with a safe, reversible fix get handled. The ones without do not get a guess dressed up as a solution, which is the whole point.

See it in action

Real conversation flows through the widget, on a sample account under the fictional Vornalis Hosting brand. Nothing loads until you press play.

0:55
Fix an HTTP 500. The site broke after edits. Panelbot finds the bad .htaccess line and repairs it.
0:58
Repair a database connection. "Error establishing a database connection" is traced to broken credentials, which are repaired and tested.
1:02
Speed up a slow site. Twenty-second page loads are traced to the resource-hungry culprit.
0:59
Clear inode exhaustion. "Disk full" with gigabytes free: the account is out of inodes. Old cache files are purged.

All 28 scenarios are in the video demo library.