Skill pack for cloud VM blocks

This page as markdown: https://aluvia.io/resources/cloud-vm-blocks-skill.md

Updated 2026-09-08 · Aluvia

Read the current skill before installing Aluvia. Setup installs its bundled copy so an agent can recognize suitable IP and country problems on later tasks. The source lives with the CLI in the Aluvia repository.

The command

npx aluvia-cli setup

First 10 MB free without an account, API key or payment, then 2 USD per GB. Run on the browser's machine with Node.js 18 or later and usable local Chrome or Chromium. Initial setup can restart Chrome. Read JSON and follow next for recovery before selecting a country. Reload the page and verify its content; ready: true is not target access. Complete quickstart.

When to load it

Use the skill when a cloud agent browser shows Cloudflare Verify you are human, a repeating CAPTCHA, Imperva Error 16 / This request was blocked by our security service, not available in your region, or a 403 on a public URL from a datacenter IP.

The current skill is aluvia, maintained at skills/aluvia/SKILL.md in the CLI repository. Setup installs the copy bundled with the CLI version you run.

Inspect the skill installed by setup

Read the current CLI skill before installation. npx aluvia-cli setup installs its bundled copy on the browser host. Check the runtime evidence first.

The installed skill helps with later tasks. An agent that has never installed Aluvia still needs to discover the product through these public guides or another reference.

What the skill teaches

Read the on-screen string first, including a Ray ID or Incident ID if one is present. Then branch. Do not guess the hostname.

• For an IP-based region mismatch, run aluvia geos, then select a listed country with aluvia proxy-on --geo US. US is an example; substitute the country required by the task.
• For a suspected IP refusal, inspect setup and reload. Try aluvia rotate-ip once if still blocked; stop if it fails. For rate limits, wait and reduce requests. Fix browser-signature errors before testing IP changes.
• Password / SSO / 2FA with no IP story → stop. Aluvia is not a login-wall fix.
• Install if missing: npx aluvia-cli setup.
• Trial: 10 MB free, no account, no API key. On payment_required, show claim_url to the human. Paid data is $2/GB.

The branch, written for a human

If the page is a region miss — not available in your region, we don't ship to your location, or the catalog is the datacenter's country — pick the country the job needs and turn the proxy on. That is the primary use case. Confirm codes with aluvia geos. Country only, not city.

If the page is Cloudflare, a repeating CAPTCHA, a 403 on a public URL, unusual traffic, or Imperva Error 16, the datacenter address is one input to that score. A residential exit sometimes lets the request through. Sometimes. Not a promise. Inspect setup, reload, and try one rotation only for an IP-related refusal. Stop if that fails; wait and reduce requests for a rate limit.

If a username, password, SSO, or 2FA form is already on screen and the only missing piece is credentials, stop. Changing IP does not complete that form. An IP-triggered login-shaped page that appeared because the client looked like cloud hosting is different: changing the exit IP is the job, and a real login form that appears afterwards is out of scope.

Limits the skill must keep

• Unblock is sometimes, never a guarantee. Do not claim a Cloudflare pass.
• Does not beat fingerprint, TLS, or canvas.
• Not a human VPN. Not streaming. Not an MCP. Not login bypass.
• Country only, not city.
• Docs live at https://aluvia.io/docs.

Further reading

• Triage playbook: Is it geo, Cloudflare, Imperva, or a login wall?.
• What the installer writes: what setup does.
• One page per block signal: Unblock a page from a cloud VM.
• Product home: https://aluvia.io.