# AUTH431: Rest transport blocked

## What this means[​](#what-this-means "直接链接到 What this means")

The store's REST API did not answer on any address form this app can use.

The app tried the store's REST API at its normal address (/wp-json/...) and at WordPress's built-in fallback address (/?rest\_route=...), and neither answered. The store's website itself may be up — this is specifically the REST API being unreachable, usually a security plugin hiding it or a firewall rule blocking it.

## What to do[​](#what-to-do "直接链接到 What to do")

Export diagnostics and contact support. Retry after making the change above; retrying without it will fail the same way.

## Your data[​](#your-data "直接链接到 Your data")

No order or product data is affected.

## Troubleshoot[​](#troubleshoot "直接链接到 Troubleshoot")

1. If a security plugin hides or renames /wp-json/ (for example WP Hide), allow WordPress's built-in /?rest\_route= form as well — the app falls back to it automatically.
2. Check firewall (WAF) rules for anything matching wp-json or rest\_route and allow the store's own REST API through.
3. Test from a browser: <https://your-store.com/?rest_route=/> should return JSON, not a 403 page or the site's homepage.
4. If the server is behind a maintenance page or bot challenge, REST requests may be answered with an HTML page — disable the challenge for the REST API.

## Where to look[​](#where-to-look "直接链接到 Where to look")

When WCPOS can save this error, it is recorded on the device that raised it. Open **Store health → Logs** (the heart-pulse icon at the bottom of the navigation drawer), find the entry marked with this code and expand it: the expanded row shows the plain-language reason and the context captured at the moment of failure. For a store request, that context may include the server’s own error code (`serverCode`), the HTTP `status` or the `endpoint`; the fields shown depend on where the failure occurred. When reporting a problem, use **Copy debug info** at the top of the Logs screen (**Share debug info** on phones and tablets) rather than screenshots: it bundles the app version, connection state and the most recent errors. Logs are kept for at most 30 days, so collect them while the problem is fresh. Also copy any browser-console error that appeared before the POS was able to write its own log entry.

## Details[​](#details "直接链接到 Details")

* **Code:** `AUTH431` (`REST_TRANSPORT_BLOCKED`)
* **Severity:** error
* **Introduced in:** WCPOS 1.10.0