# Rate limited or throttled from a cloud VM

The limit is counted against the IP. A different exit IP starts a fresh count.

## Fix

```sh
npx aluvia-cli setup
aluvia proxy-on
```

Reload the page. If the limit follows the agent, `aluvia rotate-ip` gets a different exit IP and the count starts again.

## What the page says

Any of these means the site is judging the IP:

- "429 Too Many Requests"
- "Rate limit exceeded"
- "Slow down"

## Why it happens

Rate limits are usually keyed on the client IP. On a cloud VM that IP is shared with other tenants, so the budget can already be spent before the agent's first request.

Backing off helps only if the agent is the one spending the budget. When it is not, a different exit IP is the shorter path.

## What those commands do

`npx aluvia-cli setup` starts a small proxy next to the agent and aims the browser that is already running at it. It runs once per machine and restarts that browser once.

`aluvia proxy-on` sends every tab out through a residential or mobile carrier IP. `aluvia proxy-off` goes back to the machine's own IP. Neither restarts the browser — same browser, same tabs, same cookies.

The first setup starts a free trial from an install id on the machine. No account, no API key, no human in the loop.

## If it is still blocked

One exit IP can be blocked on its own. Get a different one and reload again.

```sh
aluvia rotate-ip
```

## When this is the wrong tool

A normal login wall or a paywall. If the site is asking who you are rather than whether you are a person, a different exit IP will not change the answer.

---

Source: https://aluvia.io/unblock/rate-limit