{"id":25045,"date":"2026-08-08T17:17:28","date_gmt":"2026-08-08T17:17:28","guid":{"rendered":"https:\/\/capskip.com\/?p=25045"},"modified":"2026-08-11T19:22:44","modified_gmt":"2026-08-11T19:22:44","slug":"error-key-does-not-exist","status":"publish","type":"post","link":"https:\/\/capskip.com\/zh\/error-key-does-not-exist\/","title":{"rendered":"\u5982\u4f55\u4fee\u590d ERROR_KEY_DOES_NOT_EXIST \u4e0e Wrong User Key \u9519\u8bef"},"content":{"rendered":"

Short answer: ERROR_KEY_DOES_NOT_EXIST<\/code> means the API key in your request is not a key the solver recognises. Nothing is wrong with the CAPTCHA, the sitekey or the page URL. The request never got as far as being solved. This guide covers the three things that actually cause it, the fix in all four SDKs, and why you sometimes get ERROR_WRONG_USER_KEY<\/code> instead.<\/p>\n

What ERROR_KEY_DOES_NOT_EXIST means<\/h2>\n

It comes back from \/in.php<\/code>, at submit time, before any solving starts. The API compared the key<\/code> parameter in your request against the key it is configured to accept, and did not find a match.<\/p>\n

# Submitting with a key the app does not know:\ncurl "http:\/\/127.0.0.1:8080\/in.php?key=WRONG&method=userrecaptcha&googlekey=YOUR_SITEKEY&pageurl=https:\/\/example.com"\n\nERROR_KEY_DOES_NOT_EXIST<\/pre>\n
Because it is returned at submit time you never get a captcha ID, so there is nothing to poll for on \/res.php<\/code>. If your code is looping and waiting, it is waiting on an ID that was never issued.<\/p>\n
One thing that trips people up coming from a hosted service: CapSkip is a 2captcha-compatible API that runs on your own machine<\/a>, so the key is not an account credential and it is not tied to a balance. It is a local access check on the API server. That changes what “wrong key” can even mean, which is why the fixes below are short.<\/p>\n
First, check whether key validation is even on<\/h2>\n
CapSkip ships with key validation optional. When it is off, any non-empty string works and you will never see this error. When it is on, the key has to match exactly.<\/p>\n
Open the CapSkip app, go to Settings, and look at the API server section. Two things matter there: whether key validation is enabled, and the exact key string if it is. Copy the key from that screen rather than retyping it. Most reports of ERROR_KEY_DOES_NOT_EXIST<\/code> end here.<\/p>\n
While you are in Settings, confirm the port too. A wrong port gives you a connection error rather than this one, but it is worth checking both at the same time. The setup guide<\/a> walks through the whole screen.<\/p>\n
Pass the key correctly in each SDK<\/h2>\n
All four SDKs take the same option name, and all four read the same environment variable, CAPSKIP_API_KEY<\/code>. Set it explicitly while you are debugging so there is no doubt about what is being sent.<\/p>\n
# pip install capskip\nfrom capskip import CapSkip\n\n# apiKey defaults to "capskip", which only works when\n# key validation is turned off in the app.\nsolver = CapSkip(\n    apiKey="YOUR_API_KEY",\n    host="127.0.0.1",\n    port=8080,\n)<\/pre>\n
\/\/ npm install capskip\nconst { CapSkip } = require('capskip');\n\nconst solver = new CapSkip({\n  apiKey: 'YOUR_API_KEY',\n  host: '127.0.0.1',\n  port: 8080,\n});<\/pre>\n
\/\/ composer require capskip\/capskip\nuse CapSkip\\CapSkip;\n\n$solver = new CapSkip([\n    'apiKey' => 'YOUR_API_KEY',\n    'host'   => '127.0.0.1',\n    'port'   => 8080,\n]);<\/pre>\n
\/\/ dotnet add package CapSkip\nusing CapSkip;\n\nvar solver = new CapSkipClient(\n    apiKey: "YOUR_API_KEY",\n    host:   "127.0.0.1",\n    port:   8080);<\/pre>\n
Full signatures for every method are on the CAPTCHA solving SDK<\/a> page.<\/p>\n
The three causes worth checking<\/h2>\n
1. The key never left your code<\/h3>\n
You set CAPSKIP_API_KEY<\/code> in a .env<\/code> file, but nothing loads .env<\/code> at runtime. Or you exported it in one shell and ran the script in another. The SDK falls back to its default, the default is not your key, and you get the error.<\/p>\n
Print what you are about to send. One line, and it settles the question:<\/p>\n
import os\n\n# Never print the whole key in a shared log.\nkey = os.environ.get("CAPSKIP_API_KEY", "<unset>")\nprint(len(key), repr(key[:4]))<\/pre>\n
Printing the length catches the case a masked value hides: a key that is present but empty, or one carrying a trailing newline from cat key.txt<\/code>.<\/p>\n
2. The key is right but mangled in the URL<\/h3>\n
This only bites people calling the raw API. If your key contains characters with a meaning in a query string, they have to be percent-encoded. A +<\/code> becomes a space, a &<\/code> ends the parameter early, and a #<\/code> truncates everything after it.<\/p>\n
# Wrong: curl sends this raw and the key gets cut at the &\ncurl "http:\/\/127.0.0.1:8080\/in.php?key=ab&cd&method=userrecaptcha"\n\n# Right: let curl encode the parameter for you\ncurl -G http:\/\/127.0.0.1:8080\/in.php \\\n  --data-urlencode "key=ab&cd" \\\n  --data-urlencode "method=userrecaptcha"<\/pre>\n
Or POST the parameters as a form body instead, which sidesteps the whole class of problem. MDN has a short reference on percent-encoding<\/a> if you want the exact character list. The SDKs encode for you, so this cause disappears the moment you switch to one.<\/p>\n
3. You changed the key and something is still holding the old one<\/h3>\n
A long-running worker, a Docker container built with the key baked in, a CI secret, a browser extension configured separately. The app has the new key, one caller still has the old one, and only that caller fails. If some of your requests work and others do not, this is almost always it.<\/p>\n
ERROR_KEY_DOES_NOT_EXIST vs ERROR_WRONG_USER_KEY<\/h2>\n
Two error strings, same family. Treat them as one problem with two shapes.<\/p>\n\n\n\n\n\n\n
Error<\/th>\nWhat it points at<\/th>\nFirst thing to check<\/th>\n<\/tr>\n<\/thead>\n
ERROR_KEY_DOES_NOT_EXIST<\/code><\/td>\nThe key was read and did not match a known key<\/td>\nThe key string itself, copied from Settings<\/td>\n<\/tr>\n
ERROR_WRONG_USER_KEY<\/code><\/td>\nKey validation is on and the key sent is wrong<\/td>\nWhether validation is on at all, then the string<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
In the SDKs both surface as an ApiException<\/code>, so catch that one type and read the message rather than branching on the string.<\/p>\n
from capskip import CapSkip, ApiException, NetworkException\n\nsolver = CapSkip(apiKey="YOUR_API_KEY")\n\ntry:\n    result = solver.recaptcha(\n        sitekey="YOUR_SITEKEY",\n        url="https:\/\/example.com\/page-with-recaptcha",\n    )\nexcept ApiException as e:\n    # Key problems land here, with the raw code in the message.\n    print("api rejected the request:", e)\nexcept NetworkException as e:\n    # The app is not running, or the port is wrong.\n    print("cannot reach capskip:", e)<\/pre>\n
Nearby error codes<\/h2>\n
If the key checks out, the next few failures at submit time look similar but mean something else entirely.<\/p>\n\n\n\n\n\n\n\n\n\n
Code<\/th>\nCause<\/th>\nFix<\/th>\n<\/tr>\n<\/thead>\n
ERROR_WRONG_METHOD<\/code><\/td>\nThe method<\/code> parameter is missing or misspelled<\/td>\nUse userrecaptcha<\/code>, turnstile<\/code>, geetest<\/code>, post<\/code> or base64<\/code><\/td>\n<\/tr>\n
ERROR_BAD_PARAMETERS<\/code><\/td>\nA required parameter for that method is absent<\/td>\nCheck the method’s parameter list before resubmitting<\/td>\n<\/tr>\n
ERROR_GOOGLEKEY<\/code><\/td>\nThe sitekey was rejected<\/td>\nRe-read it from the live page, not from cached source<\/td>\n<\/tr>\n
ERROR_PAGEURL<\/code><\/td>\nThe page URL is missing or malformed<\/td>\nSend the full URL including the scheme<\/td>\n<\/tr>\n
Connection refused<\/td>\nThe app is not running or the port differs<\/td>\nStart CapSkip, confirm the API server is on<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Every code the API can return is listed in the API documentation<\/a>.<\/p>\n
Frequently asked questions<\/h2>\n
\n\n
Do I need an API key at all?<\/h3>\n<\/summary>\n
Only if key validation is enabled in the app. With it off, any non-empty string is accepted and the SDK default of capskip<\/code> works fine. The key is a local access check, not an account.<\/p>\n<\/details>\n
\n\n
Can ERROR_KEY_DOES_NOT_EXIST mean I ran out of credit?<\/h3>\n<\/summary>\n
No. There is no balance to run out of. Solving happens on your own machine, so a key error is always a mismatch between what you sent and what the app expects.<\/p>\n<\/details>\n
\n\n
Does the key go in the poll request too?<\/h3>\n<\/summary>\n
Yes. \/res.php<\/code> takes the same key<\/code> parameter as \/in.php<\/code>. If you only fixed the submit call, the poll can still fail on the old value.<\/p>\n<\/details>\n
\n\n
Why does my old 2captcha key not work here?<\/h3>\n<\/summary>\n
Because it was issued by their service and means nothing to a solver running on your machine. The API shape is the same, the credentials are not. Point your client at 127.0.0.1<\/code> and use the key from CapSkip Settings.<\/p>\n<\/details>\n
Summary<\/h2>\n
Check whether key validation is on, copy the key from Settings instead of retyping it, confirm the value actually reaches your process, and encode it properly if you are building the URL by hand. That covers effectively every occurrence of error_key_does_not_exist<\/code>.<\/p>\n
The whole class of problem gets smaller when the solver is a local captcha solver<\/a> you control: no account, no balance, no rotating credentials, and one key you can read off the screen in front of you.<\/p>\n","protected":false},"excerpt":{"rendered":"
ERROR_KEY_DOES_NOT_EXIST \u662f\u5bc6\u94a5\u4e0d\u5339\u914d\uff0c\u4e0d\u662f\u8bc6\u522b\u5de5\u5177\u574f\u4e86\u3002\u4e09\u79cd\u6210\u56e0\u3001\u56db\u4e2a SDK \u4e2d\u5404\u81ea\u7684\u4fee\u6cd5\uff0c\u4ee5\u53ca\u5b83\u548c ERROR_WRONG_USER_KEY \u7684\u533a\u522b\u3002<\/p>","protected":false},"author":1,"featured_media":25173,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Fix ERROR_KEY_DOES_NOT_EXIST in Minutes | CapSkip","rank_math_description":"ERROR_KEY_DOES_NOT_EXIST means the API key in your request is not the one CapSkip is checking. Here is how to confirm it, fix it, and stop it recurring.","rank_math_focus_keyword":"error_key_does_not_exist","footnotes":""},"categories":[70],"tags":[],"class_list":["post-25045","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-captcha"],"_links":{"self":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/25045","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/comments?post=25045"}],"version-history":[{"count":1,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/25045\/revisions"}],"predecessor-version":[{"id":25105,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/25045\/revisions\/25105"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/media\/25173"}],"wp:attachment":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/media?parent=25045"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/categories?post=25045"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/tags?post=25045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}