Troubleshooting

The site won't pair

• "Invalid or expired key" — connection keys are single-use and short-lived. Generate a fresh key from Add site in the dashboard and paste it right away.
• Registration can't reach FleetWP — the site must be able to make outbound HTTPS requests to app.fleetwp.io. Check that no firewall or security plugin is blocking outbound calls.

Signature or "time window" errors

Signed requests must land within a 5-minute window. If you see signature rejections, check the server clock — a WordPress host with a badly skewed clock will fail signature verification. Sync the server time (NTP) and retry.

The site shows "connected" but stays silent

The connector reports on a schedule via wp-cron. On low-traffic sites wp-cron may not fire often. If FleetWP raises an offline alert while the website itself is up, the connector isn't running its jobs — configure a real system cron to hit wp-cron.php on a schedule:

# crontab: run wp-cron every 5 minutes
*/5 * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1

Backups fail or never complete

• Backups run in the background and need enough disk space and PHP execution time to dump the database and archive wp-content. Very large sites on tight limits may time out — try a database-only or files-only backup to narrow it down.
• Confirm wp-cron is firing (see above) — the archive step runs on a background cron event.

Updates or login don't take effect

• One-click login issues a single-use, 2-minute token and requires an admin account on the site. If it expires, just generate a new login URL.
• Update commands require the connector to be current. If self-update is unavailable, reinstall the latest connector zip (see Install).

Still stuck?

Disconnect the site in the dashboard and pair it again with a fresh key — this clears any stale pushed configuration and re-establishes the secret.