Grok Bot is in the datacenter's country

This page as markdown: https://aluvia.io/geo/grok-bot.md

Grok Bot's session lives on a cloud VM. When Grok Bot hits a UK site blocked from a US datacenter IP, the shop is reading that host, not the operator. A .co.uk checkout, a UK catalog, or a not-available-in-your-region page is the same miss. A US VM versus a UK site is a geo restriction applied to Grok Bot's address.

Spanish and Portuguese sites do this too when Grok Bot still presents that US address: language, catalog, or a region refusal follows the VM. The example below uses GB because a US machine opening a UK page is the usual case; replace it when the page needs another country.

The command

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.

Setup starts 10 MB of trial data with no account and no API key; paid use is $2/GB.

After aluvia proxy-on --geo GB, Aluvia sends the existing browser through a residential or mobile IP in Britain. Sticky sessions last up to 30 minutes, so a checkout that spans a few pages can keep the same country IP.

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.