Troubleshooting
A site won't connect
The messages you can see when a site won't connect, from an invalid token to a blocked REST API, what each one means and how to fix it on the site.
Applies to: All plans
Most connection problems show a message in the plugin's screen in wp-admin (Tools → RS Remote Site Manager) or on the site's page in the dashboard. Find yours below.
Connecting with the account token
| Message | What it means | What to do |
|---|---|---|
| Invalid account token. | The token is wrong or was regenerated. | Copy the current token from Account token in the dashboard. |
| Site URL must use HTTPS. | The site's address starts with http://. |
Install an SSL certificate and set the WordPress and site addresses to https://. |
| Unable to resolve the host… or Host resolves to a private or reserved IP address. | The dashboard cannot reach that address from the internet. | Connect a site that is publicly reachable; local and intranet sites cannot be managed. |
| Site limit reached (… sites). | Your plan's site limit is used up. | Remove a site or choose a bigger plan; see What each plan includes. |
| Invalid response from server. | Too many attempts in a minute, or a proxy answered instead of the dashboard. | Wait a minute and try again. |
| Missing credentials in response. | The site is already on your account, or another connection was in progress. | See "You reinstalled the plugin" below. |
Connecting with an API key and secret
When you add a site by hand, paste its API Key and API Secret into the plugin, click Save Credentials and Verify Connection, then Check Connection in the dashboard. If the dashboard says This site is already connected., that address is already on your account.
The dashboard cannot reach the site
These show on the site's page after a check or a sync:
- HTTP 401: the site rejected the dashboard's signature. The key or secret in the plugin does not match; paste them again, or regenerate the secret (see Account token and site keys).
- Site returned an HTML page instead of JSON. Something in front of WordPress answered instead of the plugin: a security plugin blocking the REST API, a firewall or CDN challenge, or a maintenance page. Make sure the plugin is active and that
/?rest_route=/rsadmin/v1/is not blocked, and allow the dashboard's requests in your firewall. - HTTP 403 or a 5xx code: the host or a firewall refused or failed the request. Check the host's firewall and error log.
- A timeout or an SSL error: the site took longer than the dashboard waits, or its certificate is not valid. Open the site in a browser to check.
Staging sites behind basic authentication need the username and password under Basic Authentication (optional) when you add the site.
The plugin shows a signature error
When the plugin calls the dashboard, these can come back:
- Invalid API key or Invalid signature: the key or secret in the plugin is out of date; paste the current ones.
- Request expired: the server's clock is more than five minutes out. Ask the host to fix the time.
- Missing or invalid nonce or Nonce already used: a request was repeated, often by a caching proxy. Try again; if it keeps happening, exclude the REST API from caching.
You reinstalled the plugin
If you deleted and reinstalled the plugin on a site that is still on your account, connecting with the account token fails with Missing credentials in response. Regenerate the site's secret under Settings → API Credentials in the dashboard and paste the key and secret into the plugin, or remove the site from the dashboard and connect it again.