Skip to content
Help centre

WordPress connector troubleshooting

What to check when a site won't connect, stops checking in, or updates won't start.

"Waiting for the first check-in…" and nothing arrives

  • Choose Check in now on the plugin's settings page in WordPress (Settings › OpsDash).
  • Check the OpsDash address has no typo (copy it from OpsDash rather than typing it).
  • Check the site token is the latest one. If you made a new token, the old one no longer works.
  • Make sure the site can reach the internet. Some hosts and security plugins block outgoing requests; allow requests to your OpsDash address.
  • Make sure the site has a client in OpsDash: WordPress connections belong to a client.

It stopped checking in

  • Is the site up? Site health shows uptime.
  • Is the plugin still active? Someone may have deactivated it, or a security plugin may have.
  • Is WP-Cron switched off (DISABLE_WP_CRON)? Then it only checks in when OpsDash wakes it or a server cron runs. Add a server cron for wp-cron.php.
  • Very quiet sites miss check-ins between visits. Plugin 1.3.1 or later can be woken by OpsDash at any time; the plugin updates itself, or update it by hand.

Updates won't start

  • Check the site's page for a held notice: an old plugin with a backup bug, or a database repair in progress.
  • Check the emergency stop, Pause all WordPress updates and restores, in Settings › Site health. Whoever runs your OpsDash can also pause updates for everyone; the setting says so.
  • Packages set to Blocked never update, and Manual ones only when chosen.

The token was lost

Make a new one with Rotate token on the site's WordPress page, and paste it into the plugin. The old token stops working straight away.

Moving a site to a new address

Edit the site in OpsDash with its new address, and check the plugin still checks in. If the domain changed completely, rotate the token and paste it in again.

Removing the connector

Deactivate and delete the plugin in WordPress. In OpsDash, removing the site from Site health keeps its WordPress history under WordPress updates.

Still stuck? See what the run messages mean.