[yggtorrent] Exception (yggtorrent): Login failed: No form found on https://www3.yggtorrent.nz/ using form selector

[damien2405]

OS: Windows Server 2012 R2

.Net Runtime: .Net-Framework

Jackett Version: v0.18.545

Last Working Jackett Version: IDK

Are you using a proxy or VPN? No

[List steps to reproduce the error and details on what happens and what you expected to happen]

Sometimes i just need to test and it's work, but now after fex hours, nothing, always this error

Logged Error Messages

[garfield69]

The indexer is working for me so the issue appears to be at your end.
provide a full enhanced log and maybe the html and debug messages will give us a clue to what may be going on.
see https://github.com/Jackett/Jackett/wiki/Troubleshooting#how-to-provide-a-jackett-enhanced-log-for-a-ticket

[opsder]

Same problem here. Relogin worked for me.

[damien2405]

Sometimes its work, sometimes not... IDK why

[garfield69]

Sometimes its work, sometimes not... IDK why

the most likely reason will be some kind of intermittent issue on the YGG login server. But you will never find out what until you catch the error while you have the enhanced logging turned on.

[xxxxxaaaaaaaannnn]

Same issue, deleted and re-added the indexer and now it works.

[dr400]

Did it many times (remove and re-add indexer) but it works just for a couple of hours and fails back again ... Apparently, just clicking the "wrench" of yggtorrent to save credentials (without touching anything else) does the trick too ...

[damien2405]

The indexer is working for me so the issue appears to be at your end.
provide a full enhanced log and maybe the html and debug messages will give us a clue to what may be going on.
see https://github.com/Jackett/Jackett/wiki/Troubleshooting#how-to-provide-a-jackett-enhanced-log-for-a-ticket

Sorry, not a lot of time with my work. No problem il will try for that full logs

[garfield69]

@martabal https://github.com/Jackett/Jackett/wiki/Troubleshooting#how-to-provide-a-jackett-enhanced-log-for-a-ticket

[Potjoe-97]

log.txt
I had the issue this morning, I did a "Test" on the indexer, and recorded the output with enhanced logging. I hope this helps. I confirm that opening the configuration and save it again, without any change, fixes it for some time after what it fails again.

[Alphachoups]

Same problem here since several Weeks.

jackett.log

[samimaarouf]

Same problem too

[Razor648]

Same problem since last week

[damien2405]

Hi @garfield69 , i dont have enough Time because of work.

But @Alphachoups make log. Its good for u?

[garfield69]

the logs show that every couple of hours YGG requires a re-login, however intermittently the web site is returning
www3.yggtorrent.nz | 524: A timeout occurred
which means that Jackett does not get the login form it requested in order to login and hence the error is generated.

I do not think there is anything Jackett can do about this. This is a YGG server issue possibly due to resource limits.

[damien2405]

Hum.. ok, but work perfectly fine since few months. And now its every night.. not normal

[RomLecat]

I agree, the issue seems widespread and appearing in a consistent matter, while browsing YggTorrent from browser never seems to trigger 524 errors.

Any work that can be done to mitigate the issue ? Considering manual re-login always works, perhaps some retry could be added ?

[garfield69]

perhaps some retry could be added

The yaml processor does not support this option. The indexer would have to be re-written in C#.

[Alphachoups]

which means that Jackett does not get the login form it requested in order to login and hence the error is generated.

The error generated is not the problem, the problem is that Jackett let the tracker in fault until we manually remove/re-add it...
Do I correctly understand that the problem is that with 1 server timeout response, the Jackett service set the tracker as in fault with no automatic re-login retry?
Seams to be very strange if a one time timeout of a tracker need a manual delete and re-add of the trackers concerned... Fault tolerance/acceptance is not a new concept in 2021 😄

Beside this, as already said by @damien2405, the configuration worked fine since few months with several (real) server downtime of Yggtorrent that never requested a manual procedure to re-add the tracker to make it working again... (except for FQDN URL changing purpose of course).
From a logical perspective the problem seams to come from elsewhere or at least more complicated then a simple timeout of the server... 🙏

[ilike2burnthing]

@Alphachoups see @garfield69's last comment for why an automatic retry is not performed. All PRs are welcome.

No, a one time timeout of a tracker does not need a manual delete and re-add of the tracker.

There have been intermittent failures on YGG's end for as long as I've used it. There are 14 pages worth of issues spanning the last 3 years when searching for yggtorrent Login failed No form found. I also know from personal experience that much of the mess around #10943 and other similar issues at the time was that a fix would work for some but not others.

[hergonoway]

I've got the same observations as comments above (working with prowlarr), I'll just add that in my case re-creating the docker container (linuxserver/jackett:latest) fix this issue everytime until the error re-occurs few hours later. (I don't need to recreate flaresolver container in the process)

[Elerir]

I've got the same observations as comments above (working with prowlarr), I'll just add that in my case re-creating the docker container (linuxserver/jackett:latest) fix this issue everytime until the error re-occurs few hours later. (I don't need to recreate flaresolver container in the process)

Hi, just so you know, going to jackett admin page and opening the edit modal for yggtorrent then closing it by pressing "okay" will also fix this bug (temporarly of course). I'm however wondering if RESTARTING jackett container would fix it aswell (imho, i would say yes, but I gotta wait for this bug to occur again in order to try)

If restarting jackett container works, then we could find a way to send a restart signal everytime this bug is encountered.
I know this doesn't fix the issue in a proper way but since I do not have enough time to dig into this issue this would be OK for me at least

[matayy]

Samed issue. Sometimes its work, sometimes not...

[kujac]

I'm trying to restart automatically the jackett docker every hour or so.
I'll let you know if that works.

[kujac]

I'm trying to restart automatically the jackett docker every hour or so. I'll let you know if that works.

This works.

[protectxme]

Hi
Have you got news fort this issue ? The problem is already on

[Pandaarr]

Hi,
I have had the same problem for a while but it has been even worse for a few days since YGG enabled Cloudflare protection... I mainly use this tracker, hope you find a solution. Thanks in advance.

[hot22shot]

Same here, I scheduled a script to restart the docker every hour but now that solution is also failing.

[martabal]

No problem with using YGGcookie indexer. But that's not a permanent solution.

[tchirou]

No problem with using YGGcookie indexer. But that's not a permanent solution.

Does it download the .torrent file ? It never does on my jackett with yggcookie

[ilike2burnthing]

Make sure you're logged in and pull a new cookie, reconfigure the indexer with it and try again.

[Lyliya]

Same issue, restarting the docker every hour does not work anymore, someone has a fix ?

[Pandaarr]

Same issue, restarting the docker every hour does not work anymore, someone has a fix ?

As long as Cloudflare is activated on the YGG website, you will need to use the YggCookie tracker instead of YggTorrent.
Make sure that Jackett is updated with the latest version.
Hope there will be more stable solutions in the future :)

[almottier]

You may switch to Prowlarr, it doesn't fix the cloudflare issue, but yggcookie is working great without the need of restarting every hour.

…

On Thu, Dec 9, 2021, 16:00 PanduxM ***@***.***> wrote: Same issue, restarting the docker every hour does not work anymore, someone has a fix ? As long as Cloudflare is activated on the YGG website, you will need to use the YggCookie tracker instead of YggTorrent. Make sure that Jackett is updated with the latest version. Hope there will be more stable solutions in the future :) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#12168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJM4NEEI2AV4L2JDRPTIW3UQDACNANCNFSM5CGAH5LA> .

[Lyliya]

YGGTorrent/YGGCookie give me this error even if i can access it from my browser :/

Message: Cloudflare Error: Cloudflare has blocked this request. Probably your IP is banned for this site, check in your web browser.: FlareSolverr was unable to process the request, please check FlareSolverr logs. Message: Cloudflare Error: Cloudflare has blocked this request. Probably your IP is banned for this site, check in your web browser.

[ilike2burnthing]

FlareSolverr/FlareSolverr#234

Only current solution is to keep retrying.

[Lyliya]

It look like they disabled it because someone has flood with prowlarr :(
Sad because its the only big one we have in France. Time to configure some US indexers with bazarr until it work again :'(

[ilike2burnthing]

The UA bypass that meant FlareSolverr wasn't even needed is what they 've disabled, it is used by yggcookie.

You can still use yggtorrent and FlareSolverr, and while it will fail most of the time, it should eventually work with enough retries (and a lot of patience).
I've been trying this for the past 10mins without success 😐 ymmv

[garfield69]

for comparison, both yggtorrent and yggcookie indexers failed to pass the cloudflare check just now.
but after I reverted the yggcookie useragent=YggRobot and used the full useragent from the config, I can now use yggcookie to search on my win10 jackett without problems.

[mushuthecat]

HI,

It works for me by configuring again my cookie and installating the last flaresolverr version 2.1.0 + the last Jackett version https://github.com/FlareSolverr/FlareSolverr/releases/tag/v2.1.0

[focheur91300]

I on my side full update jackket, FlareSolverr, cookies and user-agent too.
Still the problem of connection to the account.

[ilike2burnthing]

Switch to yggtorrent

[mushuthecat]

I on my side full update jackket, FlareSolverr, cookies and user-agent too. Still the problem of connection to the account.

your jackett is running on docker ?
In my configuration im using the user agent from my flaresolver configuration:

[JigSawFr]

For more info, please take a look at this comment: FlareSolverr/FlareSolverr#596 (comment)
Should also work with Jackett ;)