Repository navigation
Stop Google serving a CAPTCHA to every profile, and fix four proxy issues - #13
Merged
Merged
Conversation
…sues Every profile got a Google CAPTCHA on every proxy, and on a clean home connection too, while untouched Chrome on the same IP searched normally. Each cause below was isolated by A/B runs on Chrome 153 (29 Sep 2026): 1. puppeteer launches Chrome with --remote-debugging-port=0, and Chrome treats an auto-assigned port as automation mode (navigator.webdriver becomes true even with --enable-automation stripped). Profiles now launch on a fixed free port. Port 0: CAPTCHA every run; fixed port: normal results. 2. The stealth plugin was written for headless Chromium. On a visible, genuine browser its patches are only detectable fakes: the plugin with zero evasions passed every run, the app's evasion set failed every run and CreepJS read "60% stealth". Visible profiles now run without it, including on the minimize-CDP engine, which used to add it even to the anti-detect build. Headless launches keep it. 3. The fingerprint script replaced navigator.webdriver even when Chrome already reported false. That one define() alone produced the CAPTCHA; it now only runs when the browser reports true. Its toString mask and getters are also rebuilt as methods, so they have no prototype and throw on new, like real built-ins. 4. The launch geo came from ipinfo alone, which put a US proxy in Lisbon and gave the profile Portuguese time and language. It is now the consensus of ipinfo, ip-api and geojs, with the pulled country as the tie-breaker, and the geo cache is keyed on the credentials so sticky sessions sharing one gateway no longer inherit each other's location. Also: proxy checks race ipinfo and geojs, so IPv6-only exits answer in about a second instead of ~31 s; a proxy created in the last 3 minutes that fails with 407 is retried before it is marked dead (Proxy-Seller activates new lists after ~20 s); and Proxy-Seller per-IP orders honour the requested count and skip addresses already in the pool. Result in the installed app with no proxy: Google normal on real Chrome and on fingerprint-chromium, CreepJS stealth 0-20% instead of 60%.
Found while entering the vendor keys and checking each vendor's dashboard: - Proxies that differ only by password could not be saved: "Unique constraint failed on (type,host,port,username)" on Froxy, PacketStream and IPRoyal. The unique index now includes the password (migration 20260929000000). - Froxy: the connector replaced the dashboard password with a SOAX-style "wifi;us;;;" string. Froxy expects "<password>;<country>;<region>;<city>;" (help.froxy.com), and each port 9000-9199 is its own session, so a pull of 5 is now ports 9000-9004. Note: Froxy residential and mobile plans also need the client IP whitelisted on the subscription. - Live Proxies has no downloadable list URL. The connector now builds the same lines as the dashboard's Proxy Generation panel: b2b.liveproxies.io:7383, user LV<id>-lv_<cc>, sticky rows on b2b-s<N> with a numeric session. - RapidProxy: "GLOBAL" upper case and an 8-digit numeric session, as the dashboard generator uses; SOCKS5 on the same host:port. - "How many: 5" with a blank session returned one rotating row on the gateway vendors; it now mints that many sticky sessions (1 still means rotating). - Typed keys vanished on switching tab or provider and after a failed pull: the panel keeps a per-provider draft and saves credentials when Pull is clicked. The Live Proxies link and the CatProxies Plan ID are now saved too. - Airproxy, MobileProxy.Space and Proxy-Solutions no longer show a country picker they cannot use.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every profile got a Google CAPTCHA on every proxy, and on a clean home connection too, while untouched Chrome on the same IP searched normally. Each cause was isolated by A/B runs on Chrome 153 (29 Sep 2026).
CAPTCHA causes fixed
--remote-debugging-port=0puts Chrome in automation mode (navigator.webdriver = true)navigator.webdriverthat was alreadyfalsePlus: geo cache keyed on credentials (sticky sessions on one gateway no longer share a location), fake
toString/getters rebuilt withoutprototype.Proxy fixes
Result (installed app, no proxy)
Google search normal on real Chrome and on fingerprint-chromium; CreepJS stealth 0-20% instead of 60%. Through shared residential proxies Google still challenges fresh sessions, which points at IP reputation; a plain-Chrome control through the same proxy is still to run.
Tests
npm test: 466 pass. Newtest/captcha-fixes.test.js;fingerprintLeaks.test.jsnow covers both webdriver cases.