# “Access Denied” on a cloud VM

The site refused the request at the edge because of where it came from. Change the exit IP and retry.

## Fix

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

Then reload the page.

## What the page says

Any of these means the site is judging the IP:

- "Access Denied"
- "You don't have permission to access this resource"

## Why it happens

An edge rule refused the request before the application saw it, usually on the IP's reputation or its owner. Cloud and hosting ranges are published, so a site can block all of them with one rule.

Nothing about the agent's session is wrong: the same cookies work as soon as the request arrives from an IP the rule does not cover.

## 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/access-denied