Playwright uses the machine's IP

This page as markdown: https://aluvia.io/geo/playwright.md

A Playwright or Puppeteer Chrome on a VM is a browser on that VM, so the site sees the datacenter country — that is why "not available in your country" Playwright runs show up in CI and in agent jobs. A synthetic user from one datacenter tests one country; a Playwright synthetic user sent to the wrong regional site from a single datacenter region is that same miss. Send Chrome through a residential or mobile IP in the country under test.

The command

npx aluvia-cli setup
aluvia geos
aluvia proxy-on --geo US

US is an example. Country only, not city. Sticky sessions last up to 30 minutes.

Hosted browser products sometimes expose a proxyCountry control. That is a different product. On a VM you already control, Playwright launches Chrome locally, and the missing piece is the exit IP. Run npx aluvia-cli setup on that VM, then aluvia proxy-on --geo US, so Chrome and Playwright tabs that are already open go through a residential or mobile IP in that country.

What this does not do

Passing a Playwright launch argument that fakes timezone or locale is not the same as changing IP location. Aluvia does not write GPS, timezone, or Accept-Language headers; those stay whatever the process already set.