# Grok Bot is in the datacenter's country

Grok Bot on a US VM presents a US address to UK and EU sites. Send the browser through a GB residential or mobile IP when that is the country the page is choosing.

Grok Bot's browser uses the VM's IP. If that machine is in the US, a UK or EU site sees a US address and returns the US page, or says the content is not available there.

## The command

```sh
npx aluvia-cli setup
aluvia geos
aluvia proxy-on --geo GB
```

The example is `GB` because a US VM opening a UK site is the usual miss. Replace it when the page needs another country. Sticky sessions last up to 30 minutes.

## The problem

Grok Bot's session lives on a cloud VM, so every request carries that machine's address. The shop or publisher treats the address as Grok Bot's country. That is how a .co.uk checkout, a UK catalog, or a not-available-in-your-region page appears when the VM is in the US.

## The solution

Run `npx aluvia-cli setup` once on the Grok Bot machine. Then `aluvia proxy-on --geo GB` so the next load leaves through a residential or mobile IP in Britain — or pass the country code the page actually requires. The US datacenter address is no longer what the site is reading.

## What this does not do

Aluvia will not play a stream or live video, and it will not walk Grok Bot through a login form. There is no city flag, and the VM's Chrome still presents its own fingerprint, TLS, and canvas. Imperva Error 16 on a trade site is `/unblock/imperva-security-service`. The generic region string, without a Grok Bot story, is `/unblock/geo-restricted`.

---

Source: https://aluvia.io/geo/grok-bot