So for the past few weeks I have been recieving an “error” from Sonarr. It says “Indexers unavailable due to failures: KickassTorrents”. It appears to be working still for the most part, as many of my shows are still downloading. I noticed today a new show I added could not be found with the automatic search or the manual search through Sonarr. So I went to kat.cr and searched there, the episode existed on there.
I’ve had this error for a few weeks, never bothered to ask about it because things seemed to continue working. It still finds some stuff so I don’t understand what is going on.
I believe their IP address may have changed. Due to the way mono caches DNS requests on some systems, the only fix is to restart Sonarr if it’s causing problems. See if that helps.
The output from https://kat.cr/ seems to enforce gzip content encoding - at least if fetched via wget/curl - apparently sonarr doesn’t handle that very well.
A quick test : curl https://kat.cr/ | gunzip
will show normal html output, but without the gzip-pipe only “garbage”.
curl -I https://kat.co/
will give
Content-Encoding: gzip
Don’t know if there’s a knob somewhere in Sonarr or the back end libraries that will enable gzip-support.
GZip is pretty standard, I’d be surprised if it didn’t handle it, though I wonder if its an issue when falling back to Curl (which would affect mono users). Debug logs will show if its falling back.
(My) debug logs no longer show any problems, searching also works.
I can’t see any local reasons that it should work again (or that it should have stopped working). Curl still shows the forced gzip-encoding, but Sonarr doesn’t appear to have a problem with it (any longer?). My guess is “something” changed again at the remote end.
