News for hackers. Stuff that matters.

A comment on Jellyfin 12.0. Parent comment

Re:Jellyfin 12.0 by bitexploder on Monday September 07, 2026 @11:03PM (#49605266)
For what it’s worth, I am very happy with Jellyfin and the *arr suite. It took a bit of agent prodding to get them all playing nicely together and bypassing Cloudflare CAPTCHAs. However, it's pretty sweet when you get it all working.
[ Parent | on HN ]
Re:Jellyfin 12.0 by scubbo on Tuesday September 08, 2026 @12:17AM (#49605561)
> bypassing Cloudflare CAPTCHAs

Can you say more about this? I've never encountered this problem in nearly a decade of running the same stack.

[ Parent | on HN ]
Re:Jellyfin 12.0 by alacritas0 on Tuesday September 08, 2026 @12:39AM (#49605653)
With the *arr stack, some of the trackers it uses to search for a torrent will present a captcha when Prowlerr queries it for a search. If you integrate FlareSolverr and set up Prowlerr to submit queries through it for the trackers that have CAPTCHAs, it won't get blocked by them.
[ Parent | on HN ]
Re:Jellyfin 12.0 by bitexploder on Tuesday September 08, 2026 @02:06AM (#49606077)
Yep. It really isn’t nefarious or abusive. I keep mine slowed down to not scan often to be considerate. Even private trackers can require it now.
[ Parent | on HN ]
Re:Jellyfin 12.0 by scubbo on Tuesday September 08, 2026 @09:50PM (#49619794)
Ah - I use Usenet, not Torrents, that'd explain it. Thanks!
[ Parent | on HN ]