HOST151: Cache shared replay
What this means
A cache in front of the store is replaying one person's API responses to everyone.
A caching layer is serving stored REST API responses without checking who is asking: the app sent two differently-authenticated probes and received the first probe's answer both times. On a live store this means one cashier could see another's data, so connecting is blocked until the cache excludes the store's API. This is a hosting-layer problem — WordPress itself always answers per-user.
Your data
Data on this device may be at risk — do not clear local data. If this persists, export diagnostics and contact WCPOS support.
Troubleshoot
- Exclude the store's REST API paths (/wp-json/ and /?rest_route=) from page caching — on LiteSpeed disable REST caching or add a no-cache rule; on WP Engine extend the WooCommerce exclusion to /wp-json/wcpos; on Sucuri set the caching level to honor Cache-Control.
- The store's API already sends Cache-Control: no-store and Vary: Authorization — the cache layer is ignoring them; point the host at those headers.
- After changing cache settings, purge the cache before reconnecting.