403 Forbidden opening a site from a cloud VM

This page as markdown: https://aluvia.io/unblock/403.md

A 403 Forbidden opening a site from a cloud VM, on a page that needs no login, is often a network rule. A residential or mobile IP sometimes gets the page. Other signals can still 403 it.

Fix

npx aluvia-cli setup
aluvia proxy-on

Then reload the page.

What the page says

Any of these is a string the page showed:

403 Forbidden
HTTP 403
Error 403

Why it happens

A 403 Forbidden opening a site from a cloud VM is often a blanket rule against the client's network, not a permission the agent is missing. Grok Bot hits this on public URLs that still load from a home connection.

If the same URL loads on a home connection, the address is the difference that is worth trying. TLS and fingerprint can still 403 the request after that.

What those commands do

npx aluvia-cli setup aims the existing Chrome at a local proxy. aluvia proxy-on sends every tab through a residential or mobile IP. Neither command restarts the browser after that first setup.

A 403 on a public URL often fires while the client is the VM's datacenter IP, before origin HTML, which is why these commands exist.

If it is still blocked

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

aluvia rotate-ip

When this is the wrong tool

If the URL is public and loads on a home connection, try a residential or mobile exit. If the 403 is an account or missing login, stop.