# HOST161: Host rate limited

## What this means[​](#what-this-means "Directe link naar What this means")

The host is rate-limiting this store's tills.

The server keeps answering 429 (too many requests) even though the app is already backing off and honoring the server's Retry-After delays. Several tills on one internet connection share one address, so per-source rate limits treat them as a single very busy client. Syncing continues automatically but will lag until the limit is raised.

## What to do[​](#what-to-do "Directe link naar What to do")

Check the details below before trying again. WCPOS retries this automatically.

## Your data[​](#your-data "Directe link naar Your data")

No order or product data is affected.

## Troubleshoot[​](#troubleshoot "Directe link naar Troubleshoot")

1. Ask the host to raise or exempt the REST API rate limit for the store's own traffic — name the shop's static IP if it has one.
2. Security services that count 30x responses toward a block (for example Sucuri's IDS) may need the store's API excluded from that counter.
3. If several tills share one connection, mention that to the host: one IP here is a whole shop, not one user.

## Where to look[​](#where-to-look "Directe link naar 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 "Directe link naar Details")

* **Code:** `HOST161` (`HOST_RATE_LIMITED`)
* **Severity:** warn
* **Introduced in:** WCPOS 1.10.0