[yggtorrent] Error: Error solving the challenge. Message: unknown error: session deleted because of page crash

[arnaudalexis]

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.12
- Last working FlareSolverr version: 3.3.8
- Operating system: Linux-5.15.0-86-generic-x86_64-with-glibc2.31
- Are you using Docker: not sure as i am using a saas provider
- FlareSolverr User-Agent (see log traces or / endpoint): Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
- URL to test this issue: https://www3.yggtorrent.qa/engine/search?category=2145&do=search&order=desc&sort=publish_date

Description

Hi, after trying different releases (3.3.8 to 3.3.12), there is an issue when trying to access Yggtorrent tracker.
I've already had a look at different topics to solve this but without success.
I'm not sure if the app is deployed via Docker as im using a Saas platform to install it on a remote server.

Here are the params sent :
{ "maxTimeout": 180000, "cmd": "request.get", "url": "https://www3.yggtorrent.qa/engine/search?category=2145&do=search&order=desc&sort=publish_date", "proxy": {} }

Env variables :
LANG=en_US.UTF-8

I'm successfully reaching iDope, TorrentQQ and Torrent[Core].

Also i've tried to replicate the issue on Windows on another network but i can't trigger the challenge.

Could my issue be related to an ip range ban on ygg side ?

Logged Error Messages

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=120.0.6099.129)\\nStacktrace:\\n#0 0x559a05ad6f83 <unknown>\\n#1 0x559a0578fb2b <unknown>\\n#2 0x559a0577716d <unknown>\\n#3 0x559a05776882 <unknown>\\n#4 0x559a05775586 <unknown>\\n#5 0x559a0577544a <unknown>\\n#6 0x559a057737e1 <unknown>\\n#7 0x559a0577418a <unknown>\\n#8 0x559a0578507c <unknown>\\n#9 0x559a0579d7c1 <unknown>\\n#10 0x559a057a36bb <unknown>\\n#11 0x559a0577492d <unknown>\\n#12 0x559a0579d459 <unknown>\\n#13 0x559a05827f1a <unknown>\\n#14 0x559a05808e53 <unknown>\\n#15 0x559a057d0dd4 <unknown>\\n#16 0x559a057d21de <unknown>\\n#17 0x559a05a9b531 <unknown>\\n#18 0x559a05a9f455 <unknown>\\n#19 0x559a05a87f55 <unknown>\\n#20 0x559a05aa00ef <unknown>\\n#21 0x559a05a6b99f <unknown>\\n#22 0x559a05ac4008 <unknown>\\n#23 0x559a05ac41d7 <unknown>\\n#24 0x559a05ad6124 <unknown>\\n#25 0x7fb78d21fea7 start_thread\\n

Screenshots

[ilike2burnthing]

There have been a few issues now of Chrome crashing for seemingly no reason. It's then stranger that only one site is causing crashes for you and not others.

Are you using a proxy or VPN? If yes, drop it. If no, try it and test your IP range theory.

[arnaudalexis]

Hi, not using a vpn nor a proxy. I've had one successfull call yesterday (challenge found and resolved) but that only happend once.
I find it strange that one call worked if the ip is banned but i will have a look.
I also confirm that it is working fine with other indexers !

[ilike2burnthing]

Unlikely to resolve your issue, but v3.3.13 is now out, please try it.

[arnaudalexis]

Hi !
I've just updated to the latest release but unfortunately issue persists.
Had a talk with somebody having the exact same crash / error with ygg.
I don't know if i can provide more logs than what i did in my first post but i will use other indexers for now !

Have a nice day

[arnaudalexis]

Quick update, requests are still crashing. I can access the website with a browser on the same env.
I can't replicate the issue on other envs because i don't get the cloudflare challenge there.
It takes from 10 to 25 s before crashing.

[sgelineau17]

Hello,

Any feedback ?
I have the same problem on my side.

Thanks

[ilike2burnthing]

Any updates will be posted here. I can't recreate the issue, so this is reliant on a contribution, a definite cause being identified, or an update to our dependencies which solves it out of the blue.

[arnaudalexis]

Hi, i can provide more details if needed, would enabling LOG_LEVEL debug be useful ?

[ilike2burnthing]

Feel free to provide debug logs, however similar issues tend to just show a few retries and then it crashes with no discernible cause.

[arnaudalexis]

Hi, quick follow-up, issue still occurs with 3.3.15.
Can't give you much more details, same error.

[ilike2burnthing]

Please test with v3.3.16.

[Axel4602]

Same problem here, unfortunaly with v3.3.16

[MastaG]

Based on the Dockerfile it seems Flaresolverr is using the Chromium package from the debian bullseye repository:
apt-get install -y --no-install-recommends chromium chromium-common chromium-driver
Did anybody try the official chrome browser from Google? (e.g. modify the Dockerfile to just install the official .deb package instead)

This wouldn't work for arm but perhaps it's worth a shot.

[Axel4602]

GG GUYS !!! Updated flaresolverr to .17 and Ygg indexer finally works (automatic, RSS, INTERACTIV). Thanks a lot <3 love

[u2pitchjami]

hi,
it's seems good for me since i desactived ipv6 on my unraid server

[TEALC82]

No longer works since changing domain, despite deactivating IPv6 in docker compose
sysctls: - net.ipv6.conf.all.disable_ipv6=1

[ilike2burnthing]

Are you getting the error session deleted because of page crash? If not, you're probably looking for #1036

[sodanexus]

Problem solved with the fork of Juanfrillaaa on Linux without VPN or proxy (for yggtorrent)

#1163 (comment)

[skjnldsv]

Problem solved with the fork of Juanfrillaaa on Linux without VPN or proxy (for yggtorrent)

#1163 (comment)

Doesn't work for me.
Are you on windows?