ISP proxy + personal mode: reCAPTCHA evaluation always fails (403) despite correct IP routing

[kaanbulut]

Environment

• Flow2API: Beta Beta #116 (commit 53565ec)
• Server: Ubuntu 24.04, Hetzner VPS
• Chrome: 146.0.7680.177
• nodriver: 0.48.1
• Proxy: Static Residential ISP (Astound/RCN, US Los Angeles)
• Xvfb: :99 (1920x1080x24), headless=False

Problem

reCAPTCHA tokens are generated successfully (~2800 chars), but Google's server-side evaluation always returns 403:

{"error":{"code":403,"message":"reCAPTCHA evaluation failed","status":"PERMISSION_DENIED","details":[{"reason":"PUBLIC_ERROR_SOMETHING_WENT_WRONG"}]}}

What I verified

• ✅ Browser IP = API call IP = ISP proxy IP (confirmed via api.ipify.org through ProxyForwarder)
• ✅ No HeadlessChrome in User-Agent (headless=False with Xvfb)
• ✅ No WebRTC leak (flags added)
• ✅ ProxyForwarder handles both CONNECT and plain HTTP requests
• ✅ Chrome port matches ProxyForwarder port
• ✅ navigator.webdriver = false
• ✅ 3 different clean static ISP IPs tested — all fail
• ✅ Same account works fine via manual browser on personal PC
• ✅ Token has 23000+ credits, is_active=true

What I tried

1. Residential rotating proxy (Evomi) → 1/7 success (~14%)
2. Static ISP proxy (Evomi Astound/RCN) → initially 8/8 success, then 0/30+
3. headless=True → fails
4. headless=False + Xvfb → fails
5. Playwright browser mode → fails
6. Fresh install (clean git clone) → fails
7. TZ=America/Los_Angeles → fails
8. Extra Chrome flags (disable-component-update, etc.) → fails
9. Plain HTTP forwarding fix in ProxyForwarder → fails

Key observation

Had 8 consecutive successes with ISP proxy initially, then after a Chrome crash (5 parallel requests), it never worked again — even with fresh IPs and clean install. Same Google account generates images fine from a real Windows PC browser.

Questions

1. Is there something specific about the nodriver/Chrome setup that needs configuration for reCAPTCHA to pass?
2. PR feat: personal模式打码支持代理 & 全局支持socks5h协议 #104 reported 8/8 success — what proxy provider/type was used?
3. Issue Recaptcha Error #68 reports 200 req/10min with Oxylabs ISP — is there a specific configuration that works consistently?
4. Does the personal mode work reliably for anyone currently, or is it broken upstream?

[kaanbulut]

Update: YesCaptcha API also fails Tested with YesCaptcha API:

• RecaptchaV3TaskProxylessM1 (proxyless) → token obtained, Google returns 403 - RecaptchaV3EnterpriseTask (with same ISP proxy) → token obtained, Google returns 403 This means even tokens solved by a real Windows Chrome (via YesCaptcha) are rejected when used with our API call. The issue might be related to how the API request is constructed (headers, fingerprint mismatch between captcha solver and API caller).

[ws4934]

Update: YesCaptcha API also fails Tested with YesCaptcha API:

• RecaptchaV3TaskProxylessM1 (proxyless) → token obtained, Google returns 403 - RecaptchaV3EnterpriseTask (with same ISP proxy) → token obtained, Google returns 403 This means even tokens solved by a real Windows Chrome (via YesCaptcha) are rejected when used with our API call. The issue might be related to how the API request is constructed (headers, fingerprint mismatch between captcha solver and API caller). RecaptchaV3TaskProxylessM1 （无代理）→ 获取到 token，Google 返回 403 - RecaptchaV3EnterpriseTask （使用相同的 ISP 代理）→ 获取到 token，Google 返回 403 这意味着即使通过 YesCaptcha 由真实的 Windows Chrome 解决的 token，在使用我们的 API 调用时也会被拒绝。问题可能与 API 请求的构造方式有关（头部信息、验证码解决器与 API 调用者之间的指纹不匹配）。

和ip有关。连续多次请求信用分会严重降低。需要代理池，浏览器指纹也需要处理

[qq1012827513]

Similar Flow API request failed: PUBLIC_ERROR_UNUSUAL_ACTIVITY: reCAPTCHA evaluation failed

[SilverLining1-source]

俺也一样

[SurpassHR]

Get Flow API request failed: PUBLIC_ERROR_UNUSUAL_ACTIVITY_TOO_MUCH_TRAFFIC: reCAPTCHA evaluation failed.

[Tenvy]

Generation failed: Flow API request failed: PUBLIC_ERROR_UNUSUAL_ACTIVITY_TOO_MUCH_TRAFFIC: reCAPTCHA evaluation failed

[duduloveeffy]

生成失败：流程 API 请求失败：PUBLIC_ERROR_UNUSUAL_ACTIVITY_TOO_MUCH_TRAFFIC：reCAPTCHA 验证失败

[kts-kris]

Update: YesCaptcha API also fails Tested with YesCaptcha API:

• RecaptchaV3TaskProxylessM1 (proxyless) → token obtained, Google returns 403 - RecaptchaV3EnterpriseTask (with same ISP proxy) → token obtained, Google returns 403 This means even tokens solved by a real Windows Chrome (via YesCaptcha) are rejected when used with our API call. The issue might be related to how the API request is constructed (headers, fingerprint mismatch between captcha solver and API caller). RecaptchaV3TaskProxylessM1 （无代理）→ 获取到 token，Google 返回 403 - RecaptchaV3EnterpriseTask （使用相同的 ISP 代理）→ 获取到 token，Google 返回 403 这意味着即使通过 YesCaptcha 由真实的 Windows Chrome 解决的 token，在使用我们的 API 调用时也会被拒绝。问题可能与 API 请求的构造方式有关（头部信息、验证码解决器与 API 调用者之间的指纹不匹配）。

和ip有关。连续多次请求信用分会严重降低。需要代理池，浏览器指纹也需要处理

但是实测flow2api遇到reCAPTCHA的时候，我同IP同机器，chrome打开flow手动是可以生成的，没有任何障碍