First checks

The site's overview

Open the site from Websites. The header shows the site's worker version, when it last reported, and its status. Below it, the pages of the site: Health, Plugins, Themes, Users, Core, Backups, Restores, Update rounds, Monitoring, Regression, Reports, Notes.

Health

The Health page is the place to confirm a new connection:

• Connection — whether the platform can reach the site (inbound), and when the site last called the platform (outbound). A site that is reachable one way but not the other is still fine; the page says which.
• Data — one row per dataset the platform holds about the site: plugins, themes, users, core, health, backups, worker, environment. Each row says when it was last received and over which channel. Every row should read fresh shortly after connecting; a row that stays unknown means that dataset has never arrived.
• Work waiting for the site — instructions the platform has handed the site that it has not finished yet. Normally empty.
• What needs attention — the causes the platform found and, where it can say, what a person has to do.

Use Run health check to ask again immediately.

Plugins, themes, users, core

Each page lists what the site reported, with a Sync action to ask again. From here plugins and themes are activated, deactivated, updated and deleted, and WordPress core updated — one at a time, as opposed to the scheduled update round that does them together with a backup and checks.

Monitoring

Monitoring starts automatically on the package's interval for the site's home page and any further pages you add under Regression. The Monitoring page shows the checks and their log for the last ninety days.

Backups

If the package schedules backups, the first one lands in the night window after the site was added. Take one by hand from Backups to see the whole cycle — the site packs its files and database in steps, the copies are verified, and the backup appears as restorable — before you rely on the schedule.

When something is not green

Every status in the dashboard names its cause rather than a generic failure. The Troubleshooting section is organised by what you see: a site the platform cannot reach, a worker error, a permission refused, an update that failed, a backup that did not finish, a queue that is slow.