If Hermes is opening a site, the IP is the VM

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

Two different failures get reported as region problems. One is the model itself blocked by region. The other is a Hermes cloud agent driving Chrome, and the website answering content not available in your region from the VM's IP. This page is only the website case.

The command

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

Replace US when the website is choosing a different country. Sticky sessions last up to 30 minutes.

When the failure is a website — prices, a catalog, or content not available in your region — run npx aluvia-cli setup and aluvia proxy-on --geo US on that VM. Aluvia sends the browser through a residential or mobile IP in the country the page needs.

What this does not do

Nous and Hermes model availability by region is not a browser-IP fix. If the error came from the model API, Aluvia will not clear it.