FlareSolverr: Session deleted because of page crash
Have you checked our README?
- I have checked the README
Have you followed our Troubleshooting?
- I have followed your Troubleshooting
Is there already an issue for your problem?
- I have checked older issues, open and closed
Have you checked the discussions?
- I have read the Discussions
Environment
- FlareSolverr version: 3.3.3
- Last working FlareSolverr version: 3.3.2
- Operating system: Ubuntu Server 22
- Are you using Docker: yes
Description
Hi, after upgrading to the latest version yesterday, I encountered an error which is attached in the logged error messages. Downgrading to the previous version seems to work fine.
Logged Error Messages
2023-08-31T22:12:51.942603321Z 2023-08-31 22:12:51 INFO Incoming request => POST /v1 body: {'cmd': 'request.get', 'url': 'hided', 'maxTimeout': 15000}
2023-08-31T22:12:53.972707269Z 2023-08-31 22:12:53 INFO Challenge detected. Title found: Just a moment...
2023-08-31T22:12:57.952314455Z 2023-08-31 22:12:57 ERROR Error: Error solving the challenge. Message: unknown error: session deleted because of page crash\nfrom unknown error: cannot determine loading status\nfrom tab crashed\n (Session info: chrome=116.0.5845.110)\nStacktrace:\n#0 0x563de99ec013 <unknown>\n#1 0x563de97086ec <unknown>\n#2 0x563de96f11ce <unknown>\n#3 0x563de96efcdb <unknown>\n#4 0x563de96f02fd <unknown>\n#5 0x563de9704a53 <unknown>\n#6 0x563de9705a32 <unknown>\n#7 0x563de9712faf <unknown>\n#8 0x563de9716f31 <unknown>\n#9 0x563de96f08c7 <unknown>\n#10 0x563de9712c64 <unknown>\n#11 0x563de97889bb <unknown>\n#12 0x563de9770bb3 <unknown>\n#13 0x563de973b9de <unknown>\n#14 0x563de973cd72 <unknown>\n#15 0x563de99bafa6 <unknown>\n#16 0x563de99be01d <unknown>\n#17 0x563de99bdab6 <unknown>\n#18 0x563de99be4c5 <unknown>\n#19 0x563de99c48fb <unknown>\n#20 0x563de99be846 <unknown>\n#21 0x563de9997afd <unknown>\n#22 0x563de99d7255 <unknown>\n#23 0x563de99d744f <unknown>\n#24 0x563de99e503f <unknown>\n#25 0x7fe08991fea7 start_thread\n
2023-08-31T22:12:57.952680289Z 2023-08-31 22:12:57 INFO Response in 6.01 s
2023-08-31T22:12:57.953340654Z 2023-08-31 22:12:57 INFO 172.31.32.3 POST http://172.31.32.2:8191/v1 500 Internal Server Error
Screenshots
No response
About this issue
- Original URL
- State: closed
- Created 10 months ago
- Reactions: 7
- Comments: 77 (22 by maintainers)
EDIT: thanks to @ilike2burnthing, it’s now working out of the box at v3.3.7. Just update the image you use. If you’re using
docker composeandlatesttag:docker compose downshutdown all containersdocker imagesto get the image ID of flaresolverrdocker rmi {the image ID} -fforce delete the imagedocker compose up -dlaunching all containers in the background⬇️⬇️ Below are previous solutions that are kept for keeping track purpose. Do not use them, as just updating your image will work. ⬇️⬇️
Having the same issue, seems to be related to chromium’s version, as others have already pointed out. If you want to upgrade,
apt update && apt upgrademight not work, because latestchromiumversion is119.0.6045.105-1~deb11u1. However, according to some comments here, version118seems to work.EDIT: as pointed below, that’s not
chromium=119.0.6045.105-1~deb11u1by itself that’s causing the crash-loop. Will not investigate further whyapt update && apt upgradedoesn’t work, as that’s not how Docker is intended to be used.My setup:
(EDIT: added next day) Current solution: rebuilding the image (that will use
chromium=119.0.6045.105-1~deb11u1and all dependencies updated) seems to do the trick. If you’re usingdocker compose, we will switch fromimagetobuild:Previous solution (EDIT: kept for keeping track purpose, the rebuild one is much cleaner and easier): Steps to “make it work” (for the setup pointed above):
docker exec -it -u 0 flaresolverr /bin/bashconnecting to the docker container as rootapt update && apt install wget libwebpmux3=0.6.1-2.1+deb11u2updating packages list and installing wget and libwebpmux3 to a specific version, which needed for thechromiumversion we will installwget http://security.debian.org/debian-security/pool/updates/main/c/chromium/chromium_118.0.5993.117-1~deb11u1_amd64.deb && wget http://security.debian.org/debian-security/pool/updates/main/c/chromium/chromium-common_118.0.5993.117-1~deb11u1_amd64.debgetting the specificchromiumversion that works and its dependencychromium-commondpkg -i chromium_118.0.5993.117-1~deb11u1_amd64.debinstalling specific version ofchromiumthat works, thanks to the comments on this issue. However, you’ll get an error that we’ll ignore.dpkg -i chromium-common_118.0.5993.117-1~deb11u1_amd64.debinstalling thechromium-commonpackage to the same specific version, that will fix the error from previous stepexitexiting the session inside Docker, and returning to hostdocker compose restart flaresolverrrestarting the containerAs of now, I tried the steps above 2 times and it worked.
@ilike2burnthing: don’t know if posting the comment on #936, instead of here, would have been better. The two of them seems to be similar, but you’re more experienced than me on this matter. Sorry if it’s in the wrong place.
Version 3.3.2 no longer works for ygg, it’s going to timeout :
{"status": "error", "message": "Error: Error solving the challenge. Timeout after 120.0 seconds.", "startTimestamp": 1698759671252, "endTimestamp": 1698759792042, "version": "3.3.2"}Do you have the same symptoms?
Tried v3.3.2 for yggtorrent, working
Confirmed to be the chromium package
See logs with the first request on chromium 116 and the second one on chromium 118
_flaresolverr_logs (4).txt
I can confirm that it works with v3.3.2, even when behind a VPN docker service (I use Glueten). I had no success with the latest verison however.
uname -a:
Linux Jellyflix 6.2.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 6 10:23:26 UTC 2 x86_64 x86_64 x86_64 GNU/LinuxSame problem here:
ReqId 140284832659200 Incoming request => POST /v1 body: {'maxTimeout': 55000, 'cmd': 'request.get', 'url': 'https://www3.yggtorrent.wtf/'} 2023-10-22 19:34:40 2023-10-22 19:34:40 DEBUG ReqId 140284832659200 Launching web browser... 2023-10-22 19:34:40 2023-10-22 19:34:40 DEBUG ReqId 140284832659200 Started executable:/app/chromedriverin a child process with pid: 846 2023-10-22 19:34:40 2023-10-22 19:34:40 DEBUG ReqId 140284832659200 New instance of webdriver has been created to perform the request 2023-10-22 19:34:40 2023-10-22 19:34:40 DEBUG ReqId 140284799088384 Navigating to... https://www3.yggtorrent.wtf/ 2023-10-22 19:34:40 2023-10-22 19:34:40 INFO ReqId 140284799088384 Challenge detected. Title found: Just a moment... 2023-10-22 19:34:40 2023-10-22 19:34:40 DEBUG ReqId 140284799088384 Waiting for title (attempt 1): Just a moment... 2023-10-22 19:34:41 2023-10-22 19:34:41 DEBUG ReqId 140284799088384 Timeout waiting for selector 2023-10-22 19:34:41 2023-10-22 19:34:41 DEBUG ReqId 140284799088384 Try to find the Cloudflare verify checkbox... 2023-10-22 19:34:42 2023-10-22 19:34:42 DEBUG ReqId 140284799088384 Cloudflare verify checkbox not found on the page. 2023-10-22 19:34:42 2023-10-22 19:34:42 DEBUG ReqId 140284799088384 Try to find the Cloudflare 'Verify you are human' button... 2023-10-22 19:34:42 2023-10-22 19:34:42 DEBUG ReqId 140284799088384 The Cloudflare 'Verify you are human' button not found on the page. 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for title (attempt 2): Just a moment... 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for title (attempt 2): DDoS-Guard 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): #cf-challenge-running 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): .ray_id 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): .attack-box 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): #cf-please-wait 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): #challenge-spinner 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): #trk_jschal_js 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): td.info #js_info 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for selector (attempt 2): div.vc div.text-box h2 2023-10-22 19:34:44 2023-10-22 19:34:44 DEBUG ReqId 140284799088384 Waiting for redirect 2023-10-22 19:34:45 2023-10-22 19:34:45 DEBUG ReqId 140284799088384 Timeout waiting for redirect 2023-10-22 19:34:45 2023-10-22 19:34:45 INFO ReqId 140284799088384 Challenge solved! 2023-10-22 19:34:50 2023-10-22 19:34:50 DEBUG ReqId 140284832659200 A used instance of webdriver has been destroyed 2023-10-22 19:34:50 2023-10-22 19:34:50 ERROR ReqId 140284832659200 Error: Error solving the challenge. Message: unknown error: session deleted because of page crash\nfrom unknown error: cannot determine loading status\nfrom tab crashed\n (Session info: chrome=116.0.5845.180)\nStacktrace:\n#0 0x5566d4d87023 <unknown>\n#1 0x5566d4aa36ec <unknown>\n#2 0x5566d4a8dfb7 <unknown>\n#3 0x5566d4a8d241 <unknown>\n#4 0x5566d4a8c379 <unknown>\n#5 0x5566d4a8c216 <unknown>\n#6 0x5566d4a8acdb <unknown>\n#7 0x5566d4a8b2fd <unknown>\n#8 0x5566d4a9fa53 <unknown>\n#9 0x5566d4aa0a32 <unknown>\n#10 0x5566d4aadfaf <unknown>\n#11 0x5566d4ab1f31 <unknown>\n#12 0x5566d4a8b8c7 <unknown>\n#13 0x5566d4aadc64 <unknown>\n#14 0x5566d4b239bb <unknown>\n#15 0x5566d4b0bbb3 <unknown>\n#16 0x5566d4ad69de <unknown>\n#17 0x5566d4ad7d72 <unknown>\n#18 0x5566d4d55fb6 <unknown>\n#19 0x5566d4d5902d <unknown>\n#20 0x5566d4d58ac6 <unknown>\n#21 0x5566d4d594d5 <unknown>\n#22 0x5566d4d5f90b <unknown>\n#23 0x5566d4d59856 <unknown>\n#24 0x5566d4d32b0d <unknown>\n#25 0x5566d4d72265 <unknown>\n#26 0x5566d4d7245f <unknown>\n#27 0x5566d4d8004f <unknown>\n#28 0x7f1824eb2ea7 start_thread\n 2023-10-22 19:34:50 2023-10-22 19:34:50 DEBUG ReqId 140284832659200 Response => POST /v1 body: {'status': 'error', 'message': 'Error: Error solving the challenge. Message: unknown error: session deleted because of page crash\\nfrom unknown error: cannot determine loading status\\nfrom tab crashed\\n (Session info: chrome=116.0.5845.180)\\nStacktrace:\\n#0 0x5566d4d87023 <unknown>\\n#1 0x5566d4aa36ec <unknown>\\n#2 0x5566d4a8dfb7 <unknown>\\n#3 0x5566d4a8d241 <unknown>\\n#4 0x5566d4a8c379 <unknown>\\n#5 0x5566d4a8c216 <unknown>\\n#6 0x5566d4a8acdb <unknown>\\n#7 0x5566d4a8b2fd <unknown>\\n#8 0x5566d4a9fa53 <unknown>\\n#9 0x5566d4aa0a32 <unknown>\\n#10 0x5566d4aadfaf <unknown>\\n#11 0x5566d4ab1f31 <unknown>\\n#12 0x5566d4a8b8c7 <unknown>\\n#13 0x5566d4aadc64 <unknown>\\n#14 0x5566d4b239bb <unknown>\\n#15 0x5566d4b0bbb3 <unknown>\\n#16 0x5566d4ad69de <unknown>\\n#17 0x5566d4ad7d72 <unknown>\\n#18 0x5566d4d55fb6 <unknown>\\n#19 0x5566d4d5902d <unknown>\\n#20 0x5566d4d58ac6 <unknown>\\n#21 0x5566d4d594d5 <unknown>\\n#22 0x5566d4d5f90b <unknown>\\n#23 0x5566d4d59856 <unknown>\\n#24 0x5566d4d32b0d <unknown>\\n#25 0x5566d4d72265 <unknown>\\n#26 0x5566d4d7245f <unknown>\\n#27 0x5566d4d8004f <unknown>\\n#28 0x7f1824eb2ea7 start_thread\\n', 'startTimestamp': 1697996080022, 'endTimestamp': 1697996090173, 'version': '3.3.6'} 2023-10-22 19:34:50 2023-10-22 19:34:50 INFO ReqId 140284832659200 Response in 10.151 s 2023-10-22 19:34:50 2023-10-22 19:34:50 INFO ReqId 140284832659200 172.20.0.1 POST http://127.0.0.7:8191/v1 500 Internal Server ErrorIt’s for Ygg
My docker compose:
version: "2.1" services: flaresolverr: # DockerHub mirror flaresolverr/flaresolverr:latest image: ghcr.io/flaresolverr/flaresolverr:latest environment: - LOG_LEVEL=${LOG_LEVEL:-debug} - LOG_HTML=${LOG_HTML:-false} - CAPTCHA_SOLVER=hcaptcha-solver - TZ=Europe/Paris ports: - 8191:8191 restart: unless-stoppedHello, same issue here
Anyone here having this issue on something other than Docker?
I’m running FlareSolverr in Docker and not having this problem, so it’s not a global problem.
@Gauvino what version of Docker are you running?
While that command will update Chromium, it will update 36 packages in total, so the issue may not be Chromium itself.
Or close your own issue without explaining why, and thumbs down react to my comment, that’s definitely an option as well…
Updated to latest version (3.3.7) and it works out of the box. Thanks @ilike2burnthing ! If you’re using
docker composeandlatesttag:docker compose downshutdown all containersdocker imagesto get the image ID of flaresolverrdocker rmi {the image ID} -fforce delete the imagedocker compose up -dlaunching all containers in the backgroundEverything has been working for me since I updated the chromium driver, but since this morning FlareSolverr has been crashing. I tried it in a docker container with chromium up to date and in a vm, same problem.
Came late to the party, updating to Chromium (now v119 instead of 118) nuke the instance after reboot, and fail the request before reboot anyway (still 500 Internal servor). Is there a way to target/force installation of v118 specifically?
Prowlarr message
Setup on #940
Docker 24.06
And yes maybe it’s another package but I can try to just update chromium and see if it’s this or not
Docker 3.3.6 doesn’t work But running FlareSolverr 3.3.6 (in a KVM machine) work
no work for me ( v3.3.2 )
Sorry for late response but on my side I’ve checked all of this version and none of it works except 3.3.2
Well I celebrated too soon. It wasn’t working for 3 days as I mentionned. I made the changes I mentionned above and it finally worked. So I started searching for all my missing shows on Sonarr. And then it stopped working yet again. Now I have no clue where the problem might be coming from, although it looks like YGG throws out people sending “too many” requests Sorry for the false hope
UPDATE:
Removing
HARVESTER_ENDPOINTandCAPTCHA_SOLVERin my docker-compose solved it for me As mentionned all the way down in the repo’s README: “At this time none of the captcha solvers work.” I don’t know if it’sHARVESTER_ENDPOINTorCAPTCHA_SOLVERthat did the trick for me but it did. If you get this bug and change your docker-compose, take note that I had to delete the image once more (and the container of course) for the change to properly be taken into accountSame issue here on YGGTorrent tracker:
Jackett error:
Flaresolverr container logs:
Result of uname -a on host machine :
Linux <hostname> 5.15.0-87-generic #97-Ubuntu SMP Mon Oct 2 21:09:21 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux(hostname being purposefully obfuscated)
Content of docker-compose :
I’ve tried deleting all images, all containers. Putting the container on a different network. Putting the container behind a VPN. Putting the container in a separate network with Jackett. I always get the same issue.
This has been an ongoing issue for almost 3 days
Same issue despite
Challenge solved!, this problem seems to be related to seleniumLinux media001 5.15.0-84-generic #93-Ubuntu SMP Tue Sep 5 17:16:10 UTC 2023 x86_64 x86_64 x86_64 GNU/LinuxI’ve had this issue for a few weeks now
2023-09-16T21:06:58.825335135Z 2023-09-16 21:06:58 INFO Incoming request => POST /v1 body: {‘cmd’: ‘request.get’, ‘url’: ‘https://www.xxxxxxx.com’, ‘maxTimeout’: 200000, ‘session’: 'testsession} 2023-09-16T21:07:48.819388766Z 2023-09-16 21:07:48 ERROR Error: Error solving the challenge. Message: unknown error: session deleted because of page crash\nfrom unknown error: cannot determine loading status\nfrom tab crashed\n (Session info: chrome=116.0.5845.180)\nStacktrace:\n#0 0x00556a2bef80 <unknown>\n#1 0x00556a012134 <unknown>\n#2 0x005569ffd2b0 <unknown>\n#3 0x005569ffbff4 <unknown>\n#4 0x005569ffc558 <unknown>\n#5 0x00556a00a904 <unknown>\n#6 0x00556a01b32c <unknown>\n#7 0x005569ffcb10 <unknown>\n#8 0x00556a01b054 <unknown>\n#9 0x00556a0857d4 <unknown>\n#10 0x00556a03e9f0 <unknown>\n#11 0x00556a03fc7c <unknown>\n#12 0x00556a28b1d0 <unknown>\n#13 0x00556a28e084 <unknown>\n#14 0x00556a28dc20 <unknown>\n#15 0x00556a2949c8 <unknown>\n#16 0x00556a28e78c <unknown>\n#17 0x00556a26a014 <unknown>\n#18 0x00556a2a7414 <unknown>\n#19 0x00556a2a7620 <unknown>\n#20 0x00556a2b57c8 <unknown>\n#21 0x007fb9030648 start_thread\n#22 0x007fb8853fdc <unknown>\n 2023-09-16T21:07:48.820929291Z 2023-09-16 21:07:48 INFO Response in 49.994 s
As a workaround I don’t specifically a session name. Since a few updates ago, there was a code change that would re-create the browser instance and I think the issue might of been introduced around that time.
+1 for also seeing this error, running in docker, vanilla config nothing fancy going on, same error on numerous sites.
2023-09-27 10:05:32 ERROR ReqId 140331148957440 Error: Error solving the challenge. Message: invalid session id\nStacktrace:\n#0 0x565259403023 <unknown>\n#1 0x56525911f6ec <unknown>\n#2 0x565259152137 <unknown>\n#3 0x565259187cee <unknown>\n#4 0x565259183d04 <unknown>\n#5 0x565259183525 <unknown>\n#6 0x5652590ea8e7 <unknown>\n#7 0x5652590eb8d3 <unknown>\n#8 0x5652593d1fb6 <unknown>\n#9 0x5652593d502d <unknown>\n#10 0x5652593d4ac6 <unknown>\n#11 0x5652593d54d5 <unknown>\n#12 0x5652593db90b <unknown>\n#13 0x5652593d5856 <unknown>\n#14 0x5652593aeb0d <unknown>\n#15 0x5652590ea765 <unknown>\n#16 0x5652590e9f37 <unknown>\n#17 0x7f621811fd0a __libc_start_main\n 2023-09-27 10:05:32 DEBUG ReqId 140331148957440 Response => POST /v1 body: {‘status’: ‘error’, ‘message’: ‘Error: Error solving the challenge. Message: invalid session id\nStacktrace:\n#0 0x565259403023 <unknown>\n#1 0x56525911f6ec <unknown>\n#2 0x565259152137 <unknown>\n#3 0x565259187cee <unknown>\n#4 0x565259183d04 <unknown>\n#5 0x565259183525 <unknown>\n#6 0x5652590ea8e7 <unknown>\n#7 0x5652590eb8d3 <unknown>\n#8 0x5652593d1fb6 <unknown>\n#9 0x5652593d502d <unknown>\n#10 0x5652593d4ac6 <unknown>\n#11 0x5652593d54d5 <unknown>\n#12 0x5652593db90b <unknown>\n#13 0x5652593d5856 <unknown>\n#14 0x5652593aeb0d <unknown>\n#15 0x5652590ea765 <unknown>\n#16 0x5652590e9f37 <unknown>\n#17 0x7f621811fd0a __libc_start_main\n’, ‘startTimestamp’: 1695805521685, ‘endTimestamp’: 1695805532048, ‘version’: ‘3.3.6’} 2023-09-27 10:05:32 INFO ReqId 140331148957440 Response in 10.363 s 2023-09-27 10:05:32 INFO ReqId 140331148957440 127.0.0.1 POST http://127.0.0.1:8191/v1 500 Internal Server Error
Provide the environment information requested in full, including the URL.