Jackett: [yggtorrent] Exception (yggtorrent): Error parsing JS challenge html: Error parsing JS challenge html (Test)

[RaphaelDucay]

Please use the search bar at the top of the page and make sure you are not creating an already submitted issue.
Check closed issues as well, because your issue may have already been fixed.

Please read our Contributing Guidelines before submitting your issue to ensure a prompt response to your bug.

Environment

OS:
Win10
.Net Runtime: [.Net-Core/.Net-Framework/Mono]

.Net Version:

Jackett Version:
0.16.227.0

Last Working Jackett Version:
0.16.185.0

Are you using a proxy or VPN? [yes/no]
no

Description

Tried to upgrade from 0.16.185.0 to 0.16.227.0 to solve my issue #8463
Still getting an error but different on yggtorrent indexer test (failing)

Logged Error Messages

Exception (yggtorrent): Error parsing JS challenge html: Error parsing JS challenge html (Test)

Screenshots

[Place any screenshots of the issue here if needed]

[guicha910]

Same here, I either have this error message or this one : "Exception (yggtorrent): Input string was not in a correct format.: Input string was not in a correct format.".

Updated jackett, but still same error.

[aguillem]

Same here. Try to configure YggCookie indexer instead and still have the same error.

[MartnIV]

Same error

[Atheros33]

Same here, the error is now "Exception (yggcookie): Input string was not in a correct format.: Input string was not in a correct format."

[MartnIV]

Yes, i now have the same error: "Exception (yggcookie): Input string was not in a correct format.: Input string was not in a correct format." on Yggtorrent.

Non-related question: is there any advantage to use Yggcookie over Yggtorrent?

[Miko2708]

hello same for me i'm using docker-compose on ubuntu 18.04
logJackett.txt

[bossovitch]

same here, yggtorrent cause lot of trouble lately...

[loulich]

same here: Input string was not in a correct format

[sam37git]

same here: Input string was not in a correct format

[navycrow]

+1

[ngosang]

This issue is caused by Cloudflare. They changed the JS challenge again and the library that we use to solve the challenge is abandoned. https://github.com/RyuzakiH/CloudflareSolverRe/issues
I will fix it soon, but we have to find a long term solution or more developers...

[0xAcid]

As already stated here : https://github.com/Jackett/Jackett/issues/8056#issuecomment-609989148
Using selenium to get those token is doable. I am doing it on my private yggtorrent scraper, and no issue so far.
Using selenium is not an elegant solution for sure, but it would be pretty hard for cloudflare to break it.
Just my 2 cents

[jonozzz]

torrentz2.eu is also affected by this.

[CyberPoison]

Same Issue here, Thanks if will be a fix for this.

[garfield69]

@MartnIV wrote:

Non-related question: is there any advantage to use Yggcookie over Yggtorrent?

YGGCokie has advantages and disadvantages

• the advantage is that when YGGTorrent's login method does not work then YGGCookie can usually provide an alternate method of access
• the disadvantage is that the cookie method is temporary as the cookie expires regularly and so needs fetching frequently. Also, some users on seedboxes or VPN find the cookie method does not work for them.

and right now, neither method works for me. so you will just have to use your browser for now, as Jackett cannot access the web site until the Cloudflare library is updated to handle the new challenge (hopefully).

[CyberPoison]

@garfield69 do you have any date for when the CloudFlare Library will be updated ?

[ngosang]

Update: The new challenge is more complex. They have raised the bar...

At this moment none of the CloudFlare resolvers that I know are working, the only fix is to use Selenium (It's a full web browser) to solve the challenge, but it can't be integrated into Jackett easily and I'm against anyway.
You can follow the progress here:

• https://github.com/RyuzakiH/CloudflareSolverRe/issues
• https://github.com/VeNoMouS/cloudscraper/issues/209

When there is a fix it will be implemented in Jackett but I think this is going to take a while...

[fabwardo]

Also affecting 1337x

[foux]

As already stated here : #8056 (comment)
Using selenium to get those token is doable. I am doing it on my private yggtorrent scraper, and no issue so far.
Using selenium is not an elegant solution for sure, but it would be pretty hard for cloudflare to break it.
Just my 2 cents

Any possibility to share your scraper?

[ilike2burnthing]

In terms of public indexers, it will affect all of these - https://github.com/Jackett/Jackett/issues/7325#issuecomment-603887196

@ngosang I take it this would also cause Input string was not in a correct format.?
Both shown here:
log - input string.txt
log - js challenge.txt

[garfield69]

@ilike2burnthing wrote:

I take it this would also cause Input string was not in a correct format.?

yes.

[tchirou]

Any possibility to use this ?https://github.com/RyuzakiH/CloudflareSolverRe/issues/28#issuecomment-622799060

[darkcattz]

same here: Input string was not in a correct format

[minitoaster]

same here

[ngosang]

I just cracked Cloudflare again. I think this time it will last more.
Code and package => https://github.com/RyuzakiH/CloudflareSolverRe/pull/29

Fixes all sites with Cloudflare JS: YggTorrent, Limetorrents, Torrentz2, BTDB, BTEye..
This change will be included included in the next Jackett release (when @garfield69 has time)

[tchirou]

You are the man 💪🏻
Thanks a lot !

[ilike2burnthing]

Confirmed working. Nicely done! ;)

[guicha910]

Does not work yet on docker.

[Sebclem]

Does not work yet on docker.

Docker as not been updated yet, just be patient 😉

[guicha910]

Does not work yet on docker.

Docker as not been updated yet, just be patient 😉

D'accord Seb

[garfield69]

Jackett 0.16.256

[angoody]

I still have "Exception (yggtorrent): Input string was not in a correct format.: Input string was not in a correct format." in a docker with Jackett 0.16.256

Would you like the full log?

[garfield69]

@angoody

Would you like the full log?

yes thanks. the enhanced log. see https://github.com/Jackett/Jackett/wiki/Troubleshooting#how-to-provide-a-jackett-enhanced-log-for-a-ticket

[angoody]

Here it is:

jackett log.txt

Tell me if you want more test.

[LordBilbon]

Hello, i'm still in .252 after docker update, i'm use the linuxserver.io image, another way to update docker jackett ??

[lukjod]

just wait I guess...

[angoody]

I have to create an other one issue for the error "Exception (yggtorrent): Input string was not in a correct format.: Input string was not in a correct format." ?

Tell your preference about that.

[Sebclem]

Hello, i'm still in .252 after docker update, i'm use the linuxserver.io image, another way to update docker jackett ??

For docker, switch to development tag if you can't wait for release.

And worked for me with .256

[MartnIV]

How do you change the branch on docker?

[lukjod]

like this:
docker pull linuxserver/jackett:development

[MartnIV]

Thanks, i added :development to :development into docker -compose and it worked aswell.

[angoody]

Sorry, I guess I was in 0.16.252 (updated this night)

I tried to pull linuxserver/jackett:development and it works, good work

[LordBilbon]

Yep it’s works with 256 !!

[minitoaster]

It works again with develop branch !! Thanks

Le dim. 3 mai 2020 à 20:36, LordBilbon [e-mail] a écrit :

Yep it’s works with 256 !!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Jackett/Jackett/issues/8464#issuecomment-623159218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APGDJPOHB7PYDUQHCTZJJUDRPW2TXANCNFSM4MXB2DLA
.

[RaphaelDucay]

Confirmed fix with 0.16.256 thanx ;)

[guicha910]

When will it be available on latest release on docker ? I cannot manage to change it to dev branch, too much troubles on a nas to configure everything.

[garfield69]

we are not responsible for the docker images.
the LinuxServer.io team take our builds we publish on this GitHub repo and do what ever it is that they do to create their docker images at LinuxServer.io Jackett Docker.

But if you are saying that our official stable releases are only being tagged as development by docker then that is odd because usually it gets tagged as latest
wonder what they doing when we publish a pre-release ... black hole?

you may want to contact the team via discord or discourse and follow that up.

we don't have an vested interest in chasing this and any questions you have about docker are best directed to them directly.

[ilike2burnthing]

.284 is out for :latest Docker users as of 2hrs ago, not sure why .256 never got released