Docs › Connect an agent or use the API
API troubleshooting
When a tool cannot connect.
| What you see | Likely cause and what to do |
|---|---|
| 401 wpbr_unauthenticated | If your host strips the Authorization header, the password never reaches WordPress and a correct login is refused. Ask your host to pass the header through. |
| 401 on a site that works in a browser | The front does not tell WordPress the request was https (no X-Forwarded-Proto), so WordPress refuses Application Passwords. Configure the front or host to send it. |
| Not sure why a tool cannot connect | Open Tools › Site Health: “An integration can connect to this site” lists exactly which of https, Application Passwords or background tasks is missing. |
| 403 wpbr_privileged_user | The login belongs to a user with more than the connection role. Create a new connection; do not reuse a user. |
| 403 wpbr_scope_denied | The connection was not given that ability. An administrator can change its permissions. |
| 402 wpbr_addon_required | The add-on is not active. Reading and rollback still work. |
| 409 wpbr_plan_stale | A file, a page link or a setting changed after the plan was made. Prepare a new plan. |
| 429 with Retry-After | Too many requests, or a run is already in progress. Wait the number of seconds given. |
| A run shows stalled_minutes growing | WordPress cron is not running. Set up a real cron hitting wp-cron.php, or call POST /runs/{id}/advance. |