# Playwright uses the machine's IP

Playwright or Puppeteer Chrome on a cloud VM is seen as that VM's country. Point the existing browser at a residential or mobile IP in the country the page needs.

A Playwright or Puppeteer Chrome in a cloud VM is just a browser on that VM. The site sees the datacenter country. That is why "not available in your country" shows up in CI and in agent runs.

## The command

```sh
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.

## The problem

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 an exit IP in the country the page needs.

## The solution

Run `npx aluvia-cli setup` on that VM, then `aluvia proxy-on --geo US`. Chrome and Playwright tabs that are already open go through a residential or mobile IP in that country. Country only, not city. This is not a human VPN.

## 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.

---

Source: https://aluvia.io/geo/playwright