Connection problems

"The platform cannot reach this site"

Open the site's Health page. The connection section shows the cause the last probe found and, for the causes where a person is needed, what to change. The full list with the meaning of each is in the worker section, Troubleshooting the worker. The ones seen most:

• Blocked by a firewall — the host's bot protection answered instead of the site. Allow the platform's address as the instruction on the page says. Since worker 2.3.0 the site keeps reporting and taking its work on its own meanwhile, so an unreachable site is not a neglected one. Hosting compatibility.
• Authentication failed — the site refused the workspace token. If the page says a JWT plugin is involved, exclude the worker's namespace in that plugin or bring the site to 2.3.0. Otherwise the token on the site is not the workspace's: paste the current one into the worker's settings.
• Plugin inactive — activate the worker on the site, or reinstall it.
• SSL error, DNS error — fix on the host or at the registrar; the platform notices on its next probe.
• Timeout — the host is slow; the platform asks again on a widening schedule.

You never need to tell the platform that a cause was fixed. It asks again — after minutes for a temporary cause, after hours for a structural one — and marks the site recovered on the first reachable answer. Run health check asks now.

The site was added but never connected

The worker is installed and paired in two steps — Install the worker. If the plugin is active and the site still shows as never reporting, run a health check and read the cause.

A site's data is old

Each page of a site shows when its dataset was last received and over which channel. Two situations:

• The site is reachable, and one dataset is stale. The platform's own read of that dataset failed — a timeout, an error on the site — and the failure was recorded rather than a fresher time invented. Sync on the page reads it again.
• The site is not reachable inbound, and everything is ageing. The site's own outbound calls have stopped. On a site with a firewall that is the channel that keeps data current, and it runs on the site's WP-Cron: a site with WP-Cron disabled and no system cron in its place does not call. Load a page on the site, or ask the host about cron.

The site redirects

A site whose address redirects — to https, to www, to another path — is refused when it is added, and one that starts redirecting later shows as unreachable with the redirect as the cause. Edit the site's address to the one it actually answers on. The platform never follows a redirect on an authenticated call, because a redirect would strip the credential.