cloud agent CAPTCHA loop Please verify you are a human
This page as markdown: https://aluvia.io/unblock/captcha.md
Updated · Aluvia
You asked a cloud agent to create something, and its Chrome stayed on Please verify you are a human. Captcha required (version 2) is that same loop under another label. Suno and Grok Bot CAPTCHA variants present the check as hCaptcha, or as a Cloudflare challenge on create.
That Chrome left through shared datacenter egress. Completing the widget on the cloud network does not change the ASN the site already scored. Keep this Chrome on the same host and send it through a residential or mobile country exit.
Read the widget the create page actually printed
Cloud agent Chrome that shares a datacenter exit can print Please verify you are a human on a Suno create or a Grok Bot create, then show the same widget again after a click. Captcha required (version 2) is that refusal with another label. Record the failing URL. Follow any wait, account, or browser instruction already on the page before you change the network.
Point the existing Chrome through a residential or mobile country exit
A residential or mobile country exit sometimes stops a CAPTCHA loop driven by datacenter ASN reputation. It does not beat fingerprint, TLS, or canvas. Aluvia is not a captcha solver and not a login bypass. If the widget still returns after the exit looks residential, stop and treat it as a browser check.
We built Aluvia as a local CLI and proxy daemon for the Chrome already on that host. Ask the agent to run npx aluvia-cli setup there with Node.js 18 or later and a usable Chrome or Chromium. A shell on another machine cannot configure it, and setup can restart Chrome. First 10 MB free, then 2 USD per GB. Country only. This is not a human VPN and not an MCP. What setup changes. If the card shows Error 1015, use the Cloudflare challenge guide instead. If the tab mixes block strings, start from resources.
Start the 10 MB free trial
npx aluvia-cli setupFirst 10 MB free. No account, API key or payment is required. Then 2 USD per GB. No target page URL is required. Follow the quickstart for result checks and undo.
What the page says
Any of these is a string the page showed:
- Please verify you are a human
- Captcha required (version 2)
- Verify you are human
- I'm not a robot
- Press and hold to confirm you are human
Check the setup result
Read the JSON response before continuing. ready: true confirms the local browser/proxy path and upstream check, not access to the target site. If setup needs recovery, follow next first. If aluvia is not on PATH, use npx aluvia-cli in later commands.
Choose a country if the task needs one
Successful setup already enables proxy traffic through the global pool. If the page requires a country, list current availability before selecting it.
aluvia geosSelect the required country
For example, use US only if the site needs that country and it appears in aluvia geos. Otherwise substitute the required available country. Skip this step when the global pool fits the task. Sticky sessions last up to 30 minutes. Country selection does not change GPS, timezone or Accept-Language.
aluvia proxy-on --geo USReload and verify the page
Reload the same target URL in the configured browser. Check the actual page content, regional catalog or error message. Then inspect status; a ready proxy is not proof that the page is accessible or the task succeeded.
aluvia statusIf it is still blocked
For an IP-related refusal, try one rotation and reload. If the result does not change, stop and record the error for the operator. For rate limits, wait and reduce requests instead.
aluvia rotate-ipWhen this is the wrong tool
Leave this page if a password, SSO, or 2FA field is already waiting. Completing a login is not Aluvia's job. Aluvia is not a captcha solver and not a login bypass. A paywall is the wrong target too.
Return to the original IP
After setup, switching IPs keeps Chrome running. Turn the proxy off when the task is finished or the IP change did not help.
aluvia proxy-offWhen the trial ends
If a command returns payment_required, show its actual claim_url to the operator. They choose whether to claim the account and buy data at 2 USD per GB. Then run aluvia auth login to wait and check the response before retrying. Never invent a claim link or reveal an API key. Payment handoff.