Failed to verify your browser Code 11 Vercel Security Checkpoint cloud agent
This page as markdown: https://aluvia.io/unblock/vercel-security-checkpoint.md
Updated · Aluvia
Your cloud agent's Chrome can spend the task on Vercel Security Checkpoint. We're verifying your browser is the opening line. Failed to verify your browser and Code 11 are the failure under it. A Cursor agent stuck tab is where this usually appears.
That request left datacenter egress. If the same URL loads on your laptop, the checkpoint treated the cloud address differently from your home connection. Code 99 can appear on a different Vercel card. Note it, and stay with Code 11 here.
Confirm Code 11 on the card in front of you
Vercel Security Checkpoint is the name on the card. We're verifying your browser comes first, then Failed to verify your browser and Code 11. That is cloud agent Chrome stuck on the checkpoint after datacenter egress.
Code 99 is an adjacent string on a different card. Record it, then keep this guide on Code 11.
Point the same Chrome through a country exit
A residential or mobile exit sometimes lets a Cursor or cloud agent past the checkpoint when the failure is datacenter IP reputation. It does not beat fingerprint, Linux Chrome, TLS, canvas, or BotID, and it is not a login bypass.
Leave the agent Chrome on this host and send it through a residential or mobile country exit. A residential IP comes from a home connection. A mobile IP comes from a phone network. Country only, not a city. This is not a human VPN and not an MCP.
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. The first 10 MB is free, then 2 USD per GB. After setup, aluvia geos lists countries. aluvia proxy-on --geo US selects a United States address, or name the country the job needs. What setup changes. For that Cursor host, see the Cursor host country page. If the card is Cloudflare's, use the Cloudflare block page.
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:
- Vercel Security Checkpoint
- We're verifying your browser
- Failed to verify your browser
- Code 11
- Cursor agent stuck tab
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-ipStop when a sign-in form is already on screen
If a username, password, SSO, or 2FA field is already waiting, stop. The checkpoint runs before the site answers, and it is not a sign-in form. Aluvia changes the exit for this Chrome. It does not type credentials, and it is not CapSolver.
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.