Connection and conversion troubleshooting

Resolve common failures without losing the current draft.

401: connection is not authorized

Check token expiry or revocation, current account access and whether the destination is still connected. Copying an old token or using the plugin’s private endpoint instead of the platform endpoint will not restore hosted access. Create a replacement through MCP connections when needed.

403 or destination denied

Check the domain scope of your token. An all-domains token still needs the selected site_id on each operation and cannot reach another account’s site. A read-only connection cannot create or change pages.

429: slow down

Pause requests and retry later. The gateway shares a request allowance across your account’s tokens. Creating another token will not increase it.

Connection verification fails

Confirm the destination is publicly reachable over HTTPS, the plugin is active and pairing completed. Check whether a firewall blocks the connector route. Report the short error code; do not share credentials or full logs.

A draft looks wrong or is not editable

Continue the original brief. Read the current page, inspect the failing section and reproduce the problem in both Gutenberg and the front end. Submit bounded feedback with expected versus observed behavior. A report creates an issue, not an automatic code fix.