-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[yggtorrent] Exception (yggtorrent): Login failed: No form found on https://www3.yggtorrent.nz/ using form selector #12168
Comments
The indexer is working for me so the issue appears to be at your end. |
Same problem here. Relogin worked for me. |
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. |
Same issue, deleted and re-added the indexer and now it works. |
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 ... |
Sorry, not a lot of time with my work. No problem il will try for that full logs |
log.txt |
Same problem here since several Weeks. |
Same problem too |
Same problem since last week |
Hi @garfield69 , i dont have enough Time because of work. But @Alphachoups make log. Its good for u? |
the logs show that every couple of hours YGG requires a re-login, however intermittently the web site is returning I do not think there is anything Jackett can do about this. This is a YGG server issue possibly due to resource limits. |
Hum.. ok, but work perfectly fine since few months. And now its every night.. not normal |
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 ? |
The yaml processor does not support this option. The indexer would have to be re-written in C#. |
The error generated is not the problem, the problem is that Jackett let the tracker in fault until we manually remove/re-add it... 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). |
@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 |
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. |
Samed issue. Sometimes its work, sometimes not... |
I'm trying to restart automatically the jackett docker every hour or so. |
This works. |
Hi |
Hi, |
Same here, I scheduled a script to restart the docker every hour but now that solution is also failing. |
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 |
Make sure you're logged in and pull a new cookie, reconfigure the indexer with it and try again. |
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. |
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>
.
|
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. |
Only current solution is to keep retrying. |
It look like they disabled it because someone has flood with prowlarr :( |
The UA bypass that meant FlareSolverr wasn't even needed is what they 've disabled, it is used by yggcookie.
|
for comparison, both yggtorrent and yggcookie indexers failed to pass the cloudflare check just now. |
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 |
Switch to yggtorrent |
For more info, please take a look at this comment: FlareSolverr/FlareSolverr#596 (comment) |
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
The text was updated successfully, but these errors were encountered: