{"id":24846,"date":"2026-08-04T19:27:31","date_gmt":"2026-08-04T19:27:31","guid":{"rendered":"https:\/\/capskip.com\/?p=24846"},"modified":"2026-08-04T19:27:31","modified_gmt":"2026-08-04T19:27:31","slug":"capcha-not-ready","status":"publish","type":"post","link":"https:\/\/capskip.com\/zh\/capcha-not-ready\/","title":{"rendered":"\u5982\u4f55\u5728\u8f6e\u8be2\u7ed3\u679c\u65f6\u4fee\u590d CAPCHA_NOT_READY"},"content":{"rendered":"

Short answer: CAPCHA_NOT_READY<\/code> is not an error. It is the API telling you the CAPTCHA is still being solved and you asked too early. There is nothing to fix in your request. You just need the right polling rhythm, and a loop that knows when to stop. This guide covers both, plus the read-once behaviour that turns a working script into a confusing one.<\/p>\n

What CAPCHA_NOT_READY actually means<\/h2>\n

When you submit a CAPTCHA to \/in.php<\/code> you get back an ID, not an answer. Solving happens in the background. You then poll \/res.php<\/code> with that ID until the answer is ready.<\/p>\n

Until it is, every poll returns the same string:<\/p>\n

# Poll for the result. Note action=get and the id from \/in.php.\ncurl "http:\/\/127.0.0.1:8080\/res.php?key=YOUR_API_KEY&action=get&id=CAPTCHA_ID"\n\n# Still working:\nCAPCHA_NOT_READY\n\n# Done:\nOK|03AGdBq26Sxo...<\/pre>\n
And yes, it is spelled CAPCHA<\/code>, not CAPTCHA<\/code>. That typo has been in the 2captcha API since the beginning. CapSkip is drop-in compatible with that API, so the misspelling is preserved deliberately. If it were corrected, every existing client library checking for the exact string would break. Match it exactly in your code.<\/p>\n
Poll on the right schedule<\/h2>\n
Most people hit this constantly because they poll immediately after submitting. Different CAPTCHA types take very different amounts of time, so the first check should not happen at the same moment for all of them.<\/p>\n\n\n\n\n\n\n\n\n\n
Type<\/th>\nWait before first check<\/th>\nThen retry every<\/th>\n<\/tr>\n<\/thead>\n
Image \/ text<\/td>\n1 second<\/td>\n5 seconds<\/td>\n<\/tr>\n
reCAPTCHA v2<\/td>\n15 to 20 seconds<\/td>\n5 seconds<\/td>\n<\/tr>\n
reCAPTCHA v3<\/td>\n10 to 15 seconds<\/td>\n5 seconds<\/td>\n<\/tr>\n
GeeTest<\/td>\nabout 5 seconds<\/td>\n5 seconds<\/td>\n<\/tr>\n
Cloudflare Turnstile<\/td>\nabout 5 seconds<\/td>\n5 seconds<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Polling faster than every 5 seconds does not make anything solve quicker. It just burns requests.<\/p>\n
A polling loop that terminates<\/h2>\n
The shell version, showing the shape clearly:<\/p>\n
# Submit, capture the id, give it a head start, then poll.\nID=$(curl -s "http:\/\/127.0.0.1:8080\/in.php?key=YOUR_API_KEY&method=userrecaptcha&googlekey=YOUR_SITEKEY&pageurl=https:\/\/example.com" | cut -d'|' -f2)\n\nsleep 15\nwhile :; do\n  RES=$(curl -s "http:\/\/127.0.0.1:8080\/res.php?key=YOUR_API_KEY&action=get&id=$ID")\n  [ "$RES" = "CAPCHA_NOT_READY" ] || break\n  sleep 5\ndone\necho "$RES"<\/pre>\n
That loop has a flaw worth naming: it runs forever if something goes wrong upstream. In real code, cap it.<\/p>\n
# pip install requests\nimport time\nimport requests\n\nBASE = "http:\/\/127.0.0.1:8080"\n\ndef solve_recaptcha(sitekey, page_url, api_key="YOUR_API_KEY", timeout=180):\n    task = requests.get(BASE + "\/in.php", params={\n        "key": api_key,\n        "method": "userrecaptcha",\n        "googlekey": sitekey,\n        "pageurl": page_url,\n        "json": 1,\n    }).json()\n    task_id = task["request"]\n\n    time.sleep(15)                      # reCAPTCHA needs a head start\n    deadline = time.monotonic() + timeout\n\n    while time.monotonic() < deadline:\n        res = requests.get(BASE + "\/res.php", params={\n            "key": api_key,\n            "action": "get",\n            "id": task_id,\n        }).text.strip()\n\n        if res.startswith("OK|"):\n            return res.split("|", 1)[1]\n\n        # Anything that is not the pending string is terminal.\n        if res != "CAPCHA_NOT_READY":\n            raise RuntimeError(res or "empty response: already read, or bad id")\n\n        time.sleep(5)\n\n    raise TimeoutError("gave up after %ss" % timeout)<\/pre>\n
Three things make this safe: a deadline so it cannot hang, treating any non-pending string as terminal so real errors surface immediately, and reading the answer exactly once.<\/p>\n
Or skip the loop entirely<\/h2>\n
If you are using one of the official SDKs, none of the above is your problem. Polling happens inside the call and you get the token back directly, so CAPCHA_NOT_READY<\/code> never reaches your code.<\/p>\n
# pip install capskip\nfrom capskip import CapSkip\n\nsolver = CapSkip(host="127.0.0.1", port=8080)\n\n# Submit and poll happen inside this one call.\nresult = solver.recaptcha(\n    sitekey="YOUR_SITEKEY",\n    url="https:\/\/example.com\/page-with-recaptcha",\n)\n\nprint(result["code"])   # token, ready to inject<\/pre>\n
\/\/ npm install capskip\nconst { CapSkip } = require('capskip');\n\nconst solver = new CapSkip({ host: '127.0.0.1', port: 8080 });\nconst result = await solver.recaptcha('YOUR_SITEKEY', 'https:\/\/example.com\/page-with-recaptcha');\n\nconsole.log(result.code);<\/pre>\n
\/\/ composer require capskip\/capskip\nuse CapSkip\\CapSkip;\n\n$solver = new CapSkip(['host' => '127.0.0.1', 'port' => 8080]);\n$result = $solver->recaptcha('YOUR_SITEKEY', 'https:\/\/example.com\/page-with-recaptcha');\n\necho $result['code'];<\/pre>\n
\/\/ dotnet add package CapSkip\nusing CapSkip;\n\nvar solver = new CapSkipClient(host: "127.0.0.1", port: 8080);\nvar result = await solver.RecaptchaAsync("YOUR_SITEKEY", "https:\/\/example.com\/page-with-recaptcha");\n\nConsole.WriteLine(result.Code);<\/pre>\n
Full method signatures for all four languages are on the CAPTCHA solving SDK<\/a> page. The raw loop above is still what you want for Go, Java, Ruby, or anything without an official package.<\/p>\n
The read-once trap<\/h2>\n
This is the one that wastes an afternoon. Each result can be read only once.<\/strong> Poll again after a successful read and you get an empty response, not the token you already had.<\/p>\n
So an empty body does not mean “still working”. It means one of two things:<\/p>\n