A DrissionPage captcha step is three moves: read the sitekey off the page, send it to a solver, then write the token back into the form with JavaScript. DrissionPage drives a real Chrome over the DevTools Protocol instead of a webdriver, so the browser side is simpler than Selenium. The element model is not, and it has one default that turns a missing widget into an error from the solver instead of an error from your locator. That default is the reason most of these scripts fail confusingly, so it gets its own section.<\/p>\n
# Both packages, one line.\npip install DrissionPage capskip<\/pre>\n<\/div>\nWhy DrissionPage changes the shape of this<\/h2>\n
DrissionPage talks to Chrome over CDP directly. There is no chromedriver process in the middle, so there is no driver binary to patch and no separate service to keep in step with your browser version. It also attaches to a browser that is already running, which is genuinely useful here: you can log in by hand once, leave the profile open, and let the script pick up the session.<\/p>\n
What does not change is the token. A solved reCAPTCHA is a string that has to end up in the hidden
g-recaptcha-response<\/code> textarea before you submit. That textarea isdisplay:none<\/code>, so typing into it is not an option in any automation tool. You write it with JavaScript, and DrissionPage’s run_js method is how you do it.<\/p>\nOne thing worth being straight about: no webdriver does not mean no detection. Running Chrome over CDP removes one signal, and leaves the rest of your fingerprint exactly where it was. Solving the challenge is a separate job from looking like a browser, and this post only covers the first.<\/p>\n
Step 1: read the sitekey off the page<\/h2>\n
The sitekey sits on the host document, not inside the widget iframe. Google’s own markup puts it on a container element as
data-sitekey<\/code>, and DrissionPage’s attribute locator finds it without a CSS selector.<\/p>\n\n# pip install DrissionPage\nfrom DrissionPage import ChromiumPage\n\npage = ChromiumPage()\npage.get("https:\/\/example.com\/page-with-recaptcha")\n\n# @attr finds by attribute. The default search timeout is 10s,\n# which is plenty for a widget that renders on load.\nholder = page.ele("@data-sitekey")\nsitekey = holder.attr("data-sitekey")\n\nprint(sitekey) # 6Lxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<\/pre>\n<\/div>\nDrissionPage’s locator prefixes are worth learning here, because they replace most of the XPath you would otherwise write: @attr=value matches exactly, @attr:value matches a substring, @attr^value matches the start, and @attr$value matches the end. Prefixing a locator with a tag name, as in tag:iframe, pins the element type as well.<\/p>\n
Some sites never put the sitekey on the host page and only pass it in the iframe URL. Read it from there instead, using contains to match the frame you want.<\/p>\n
\n# Fallback: the k= query parameter on the widget iframe.\nfrom urllib.parse import urlparse, parse_qs\n\nframe = page.ele("tag:iframe@src:recaptcha\/api2\/anchor")\nsrc = frame.attr("src")\nsitekey = parse_qs(urlparse(src).query)["k"][0]<\/pre>\n<\/div>\nStep 2: solve it against the local API<\/h2>\n
The solver runs on your own machine on port 8080 and speaks the 2captcha API, so the SDK call is one line and there is no per solve billing behind it. Pass the page URL from
page.url<\/code> rather than retyping it, because a redirect betweenget()<\/code> and the solve would otherwise leave you submitting the wrong URL.<\/p>\n\n# pip install capskip\nfrom capskip import CapSkip\n\nsolver = CapSkip(host="127.0.0.1", port=8080)\n\n# Same call shape for v3 (version="v3") and Enterprise (enterprise=1).\nresult = solver.recaptcha(sitekey=sitekey, url=page.url)\n\ntoken = result["code"] # the g-recaptcha-response value<\/pre>\n<\/div>\nTurnstile and GeeTest have methods of their own, solver.turnstile() and solver.geetest(), and both take the same shape as the call above. The full parameter list for each is in the CapSkip API documentation<\/a>.<\/p>\n
Step 3: inject the token and submit<\/h2>\n
DrissionPage passes extra arguments to
run_js<\/code> positionally, and the script reads them asarguments[0]<\/code> and so on. Pass the token as an argument rather than building the JavaScript with an f-string: a token is long, opaque and occasionally full of characters you do not want to think about quoting.<\/p>\n\n# Extra args arrive as arguments[0], arguments[1], ...\npage.run_js(\n "document.getElementById('g-recaptcha-response').value = arguments[0];",\n token,\n)\n\n# Then submit the form the way the page expects.\npage.ele("tag:button@type=submit").click()<\/pre>\n<\/div>\nIf the site defines a callback rather than reading the textarea on submit, call it after setting the value. That is a site-specific function name, so read it out of the page’s own markup instead of guessing, and note that this is still ordinary reCAPTCHA v2: the callback changes how you hand the token over, not how it gets solved. The reCAPTCHA v2 solver page<\/a> covers both submission styles.<\/p>\n
The silent failure that costs the most time<\/h2>\n
DrissionPage ships with Settings.raise_when_ele_not_found set to False. A locator that matches nothing does not raise. It returns a NoneElement, which is falsy and compares equal to Python’s None, and your script keeps going.<\/p>\n
That is a deliberate design choice and it is pleasant when you are probing optional elements. It is unpleasant here, because the next thing you do is read an attribute, and the error you get names the locator rather than the widget. Worse is the case where the element genuinely exists but carries no data-sitekey attribute at all. Then attr() hands back None, that None travels all the way to the solver as an empty key, and the failure finally surfaces as ERROR_GOOGLEKEY<\/a> from an API call you were not suspicious of.<\/p>\n
Two lines fix it. Turn raising on, and check the sitekey before you spend a solve on it.<\/p>\n
\n# Make a missing element fail where it happened.\nfrom DrissionPage.common import Settings\n\nSettings.set_raise_when_ele_not_found(True)\n\n# And still check the value, because a found element can hold nothing.\nif not sitekey:\n raise RuntimeError("No sitekey on the page. Check the widget rendered.")<\/pre>\n<\/div>\nFull working example<\/h2>\n
Everything above, in one script. The finally block matters more than usual because DrissionPage can attach to a browser you did not start, and quitting one you inherited is rarely what you want.<\/p>\n
\n# pip install DrissionPage capskip\nfrom DrissionPage import ChromiumPage\nfrom DrissionPage.common import Settings\nfrom capskip import CapSkip\n\nSettings.set_raise_when_ele_not_found(True)\n\nPAGE_URL = "https:\/\/example.com\/page-with-recaptcha"\npage = ChromiumPage()\nsolver = CapSkip(host="127.0.0.1", port=8080)\n\ntry:\n page.get(PAGE_URL)\n sitekey = page.ele("@data-sitekey").attr("data-sitekey")\n if not sitekey:\n raise RuntimeError("Widget found but data-sitekey was empty.")\n\n result = solver.recaptcha(sitekey=sitekey, url=page.url)\n page.run_js(\n "document.getElementById('g-recaptcha-response').value = arguments[0];",\n result["code"],\n )\n page.ele("tag:button@type=submit").click()\n page.wait.doc_loaded()\n\n print(page.title) # the page you land on after submitting\nfinally:\n page.quit()<\/pre>\n<\/div>\nRunning the solver on another machine<\/h2>\n
Scrapers get moved to a server sooner or later, and DrissionPage moves with them: it needs a Chromium binary and a display buffer, not much else. The solver does not have to follow it onto the same box.<\/p>\n
CapSkip has two connection modes. Local<\/strong> binds to 127.0.0.1 and is reachable only from that device, which is the right setting while you are writing the script. Server<\/strong> binds to your network or public IP, so a scraping VM, a container host or a second workstation can call the same solver over the API. A static public IP keeps that address stable. Nothing else in the code changes except the host address you pass in, and the pricing does not change either, because it is still your hardware.<\/p>\n
\n# Same SDK, same call. Only the host moves.\nsolver = CapSkip(host="10.0.0.12", port=8080, apiKey="YOUR_API_KEY")<\/pre>\n<\/div>\nTurn on key validation once the solver is listening on a network address, and give each machine its own key so one can be revoked without touching the others. The setup guide<\/a> walks through both modes.<\/p>\n
Common errors and what they mean<\/h2>\n
\n\n
\n \nWhat you see<\/th>\n Cause<\/th>\n Fix<\/th>\n<\/tr>\n<\/thead>\n \n ElementNotFoundError on attr()<\/td>\n The locator matched nothing and returned NoneElement<\/td>\n Widen the locator, or wait for the widget to render<\/td>\n<\/tr>\n \n Script continues past a missing element<\/td>\n raise_when_ele_not_found defaults to False<\/td>\n Settings.set_raise_when_ele_not_found(True)<\/td>\n<\/tr>\n \n ERROR_GOOGLEKEY<\/td>\n attr() returned None and an empty key was submitted<\/td>\n Check the value, or read the k parameter off the iframe<\/td>\n<\/tr>\n \n NetworkException<\/td>\n CapSkip is not running or the host is wrong<\/td>\n Start the app, or point host at the server address<\/td>\n<\/tr>\n \n TimeoutException<\/td>\n The solve outlasted recaptchaTimeout<\/td>\n Raise it above the default 300 seconds<\/td>\n<\/tr>\n \n Form rejects a token that solved fine<\/td>\n The token aged out before submit<\/td>\n Solve immediately before submitting, not on page load<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n FAQ<\/h2>\n
\n\n
Should I use ChromiumPage or the newer Chromium class?<\/h3>\n<\/summary>\n
Either. Version 4.1 exports Chromium, ChromiumPage, SessionPage and WebPage from the top level package, and ChromiumPage is still the shortest route to one tab. The CAPTCHA work is identical whichever you pick, because the sitekey read, the solve and the token injection all happen through the tab object.<\/p>\n<\/details>\n
\n\n
Do I need to switch into the reCAPTCHA iframe?<\/h3>\n<\/summary>\n
No, and that is the part people over-engineer. The checkbox lives in an iframe, but the sitekey attribute and the hidden response textarea both belong to the host document. You only touch a frame when the site withholds the sitekey from the page and you have to read it out of the frame’s own URL.<\/p>\n<\/details>\n
\n\n
Why does my script pass a None sitekey without complaining?<\/h3>\n<\/summary>\n
Because DrissionPage’s default is to return a falsy placeholder rather than raise, and because an element that exists can still lack the attribute you asked for. Both paths end with a None in a variable you assumed was a string. Turn raising on at the top of the file and add an explicit check on the value, which together cover both cases.<\/p>\n<\/details>\n
\n\n
My scraper runs on a VPS. Where does the solver go?<\/h3>\n<\/summary>\n
Wherever you like, as long as the two can reach each other. Server mode makes the solver listen on a network address instead of the loopback address, so the VPS calls it over the API exactly as it would any internal service. Point the host argument at that address, enable key validation, and give the VPS its own key.<\/p>\n<\/details>\n
The short version<\/h2>\n
Read the sitekey with an attribute locator, solve it on
127.0.0.1:8080<\/code>, inject the token withrun_js<\/code> and positional arguments, then submit. Turnraise_when_ele_not_found<\/code> on before you do any of it, because the default hides exactly the failure you will hit first. For the wider Python picture, including Selenium and Playwright, see the Python CAPTCHA solver page<\/a>. And because the solver is a local captcha solver<\/a> rather than a metered service, a crawl that retries a thousand pages costs the same as one that retries ten.<\/p>\n","protected":false},"excerpt":{"rendered":"DrissionPage \u901a\u8fc7 CDP \u9a71\u52a8\u771f\u5b9e\u7684 Chrome\uff0c\u6240\u4ee5 token \u4ecd\u7136\u8981\u9760 JavaScript \u5199\u8fdb\u53bb\u3002\u8bfb\u51fa sitekey\uff0c\u5728 127.0.0.1 \u4e0a\u8bc6\u522b\uff0c\u7528 run_js \u6ce8\u5165\uff0c\u5e76\u5f53\u5fc3\u90a3\u4e2a\u4f1a\u9759\u9ed8\u5931\u8d25\u7684\u5143\u7d20\u3002<\/p>","protected":false},"author":1,"featured_media":25463,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"DrissionPage CAPTCHA: Read, Solve, Inject | CapSkip","rank_math_description":"A drissionpage captcha step is three moves: read the sitekey, solve it on 127.0.0.1, inject the token with run_js. Plus the trap that hides failures.","rank_math_focus_keyword":"drissionpage captcha","footnotes":""},"categories":[70],"tags":[],"class_list":["post-25464","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\/25464","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=25464"}],"version-history":[{"count":1,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/25464\/revisions"}],"predecessor-version":[{"id":25467,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/25464\/revisions\/25467"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/media\/25463"}],"wp:attachment":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/media?parent=25464"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/categories?post=25464"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/tags?post=25464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}