FlareSolverr: [2.2.9] frameId not supported RemoteAgentError

Haven’t had much time to look closer into the issue but I’ve made some observations. In v2.2.9 the error is a result of Puppeteer thinking the first request (https://github.com/FlareSolverr/FlareSolverr/blob/master/src/services/solver.ts#L140) never finished (timeout). But when you check what’s going on without headless mode you can see the page did load and the challenge does get solved. My guess is that they changed the challenges, adding something to exploit this Puppeteer behavior. There have been sites that have done something similar before and the trick there is usually to make it not load a certain JS file. But this doesn’t work with CF because of the nature of the challenges so I’m not sure what the solution here might be at this point. But I’m pretty sure it would have to be fixed on the Puppeteer side because Selenium doesn’t have this issue.

In FlareSolverr v3 I think it’s just the challenge detection that is broken (flaresolverr_service.py#182):

challenge_found = False
for selector in CHALLENGE_SELECTORS:
    found_elements = driver.find_elements(By.CSS_SELECTOR, selector)
    if len(found_elements) > 0:
        challenge_found = True
        logging.info("Challenge detected. Selector found: " + selector)
        break

Replacing it with this solves the timeout issue until there’s a proper fix:

challenge_found = False
time.sleep(5)

I’ve also noticed the challenges solve significantly faster now than they used to.

And here is the same with last 3.0.0.beta3: curl -L -X POST ‘http://127.0.0.1:8191/v1’
-H ‘Content-Type: application/json’
–data-raw ‘{ “cmd”: “request.get”, “url”:“https://nnmclub.to/forum/login.php”, “maxTimeout”: 60000 }’ {“status”:“error”,“message”:“Error: Unable to process browser request. ProtocolError: Protocol error (Page.navigate): frameId not supported RemoteAgentError@chrome://remote/content/cdp/Error.jsm:29:5\nUnsupportedError@chrome://remote/content/cdp/Error.jsm:106:1\nnavigate@chrome://remote/content/cdp/domains/parent/Page.jsm:103:13\nexecute@chrome://remote/content/cdp/domains/DomainCache.jsm:101:25\nexecute@chrome://remote/content/cdp/sessions/Session.jsm:64:25\nexecute@chrome://remote/content/cdp/sessions/TabSession.jsm:67:20\nonPacket@chrome://remote/content/cdp/CDPConnection.jsm:248:36\nonMessage@chrome://remote/content/server/WebSocketTransport.jsm:89:18\nhandleEvent@chrome://remote/content/server/WebSocketTransport.jsm:71:14\n”,“startTimestamp”:1669583526288,“endTimestamp”:1669583549949,“version”:“v2.2.10”}

same here.

curl -L -X POST ‘http://192.168.1.168:8191/v1’ \  ✔  04:25:49 PM -H ‘Content-Type: application/json’
–data-raw ‘{ “cmd”: “request.get”, “url”:“https://kp.m-team.cc/takelogin.php”, “maxTimeout”: 60000}’ {“status”:“error”,“message”:“Error: Unable to process browser request. ProtocolError: Protocol error (Page.navigate): frameId not supported RemoteAgentError@chrome://remote/content/cdp/Error.jsm:29:5\nUnsupportedError@chrome://remote/content/cdp/Error.jsm:106:1\nnavigate@chrome://remote/content/cdp/domains/parent/Page.jsm:103:13\nexecute@chrome://remote/content/cdp/domains/DomainCache.jsm:101:25\nexecute@chrome://remote/content/cdp/sessions/Session.jsm:64:25\nexecute@chrome://remote/content/cdp/sessions/TabSession.jsm:67:20\nonPacket@chrome://remote/content/cdp/CDPConnection.jsm:248:36\nonMessage@chrome://remote/content/server/WebSocketTransport.jsm:89:18\nhandleEvent@chrome://remote/content/server/WebSocketTransport.jsm:71:14\n”,“startTimestamp”:1668846350059,“endTimestamp”:1668846355478,“version”:“v2.2.10”}

Hello, using beta v2 and v3, I’m also facing this error Challenge detected. Selector found: #trk_jschal_js. It is stuck then it times out. Hopefully a new version will fix this

@karanrahar Thanks.

Maintainers, would you mind tagging beta releases on Github too?

EDIT: I use a package manager to install Flaresolverr, which gets releases from GitHub tags, but it would be great to create a beta package too.

I’m having the same problem with m-team

“Error: Unable to process browser request. ProtocolError: Protocol error (Page.navigate): frameId not supported RemoteAgentError@chrome://remote/content/cdp/Error.jsm:29:5\nUnsupportedError@chrome://remote/content/cdp/Error.jsm:106:1\nnavigate@chrome://remote/content/cdp/domains/parent/Page.jsm:103:13\nexecute@chrome://remote/content/cdp/domains/DomainCache.jsm:101:25\nexecute@chrome://remote/content/cdp/sessions/Session.jsm:64:25\nexecute@chrome://remote/content/cdp/sessions/TabSession.jsm:67:20\nonPacket@chrome://remote/content/cdp/CDPConnection.jsm:248:36\nonMessage@chrome://remote/content/server/WebSocketTransport.jsm:89:18\nhandleEvent@chrome://remote/content/server/WebSocketTransport.jsm:71:14\n”

Updating to 3.0.0.beta3 has solved this problem for me.

New problems with beta have started:

Challenge detected. Selector found: #trk_jschal_js Error: Error solving the challenge.

I’m guessing some 3rd party component got updated and caused this haywire…

I tried ghcr.io/flaresolverr/flaresolverr:latest and ngosang/flaresolverr:3.0.0.beta3. I hope someone can solve it. thank you

curl -L -X POST 'http://localhost:8191/v1' -H 'Content-Type: application/json' --data-raw '{
  "cmd": "request.get",
  "url":"https://kp.m-team.cc/movie.php",
  "maxTimeout": 60000
}'

{"status":"error","message":"Error: Unable to process browser request. ProtocolError: Protocol error (Page.navigate): frameId not supported RemoteAgentError@chrome://remote/content/cdp/Error.jsm:29:5\nUnsupportedError@chrome://remote/content/cdp/Error.jsm:106:1\nnavigate@chrome://remote/content/cdp/domains/parent/Page.jsm:103:13\nexecute@chrome://remote/content/cdp/domains/DomainCache.jsm:101:25\nexecute@chrome://remote/content/cdp/sessions/Session.jsm:64:25\nexecute@chrome://remote/content/cdp/sessions/TabSession.jsm:67:20\nonPacket@chrome://remote/content/cdp/CDPConnection.jsm:248:36\nonMessage@chrome://remote/content/server/WebSocketTransport.jsm:89:18\nhandleEvent@chrome://remote/content/server/WebSocketTransport.jsm:71:14\n","startTimestamp":1670993493738,"endTimestamp":1670993515343,"version":"v2.2.10"}

{"status": "error", "message": "Error: Error solving the challenge. Timeout after 60.0 seconds.", "startTimestamp": 1670994910465, "endTimestamp": 1670994971205, "version": "3.0.0.beta3"}

FlareSolverr was unable to process the request, please check FlareSolverr logs. Message: Error: Unable to process browser request. ProtocolError: Protocol error (Page.navigate): frameId not supported RemoteAgentError@chrome://remote/content/cdp/Error.jsm:29:5 UnsupportedError@chrome://remote/content/cdp/Error.jsm:106:1 navigate@chrome://remote/content/cdp/domains/parent/Page.jsm:103:13 execute@chrome://remote/content/cdp/domains/DomainCache.jsm:101:25 execute@chrome://remote/content/cdp/sessions/Session.jsm:64:25 execute@chrome://remote/content/cdp/sessions/TabSession.jsm:67:20 onPacket@chrome://remote/content/cdp/CDPConnection.jsm:248:36 onMessage@chrome://remote/content/server/WebSocketTransport.jsm:89:18 handleEvent@chrome://remote/content/server/WebSocketTransport.jsm:71:14

+1 with this issue

+1 with this issue