songspolt.blogg.se

Sonarr kickass not working
Sonarr kickass not working












sonarr kickass not working
  1. #Sonarr kickass not working manual
  2. #Sonarr kickass not working full

Waiting now to see how Sonarr will handle the downloaded file and what magic will/will not .Torznab.TorznabException: Torznab error detected: : Exception (kickasstorrent): Resource temporarily unavailable Taking this topic up on the Plex forums.Ĭan’t believe most of this is up and running now. Went into this w/the notion Plex could be used without an account locally, on the local network. With an account, I am getting media to display on other devices. Take that back - just updated and now it seems sign in is required…that is a topic for another thread. Transmission is working as expected, and I think the red bars are really more about the need to add more indexers and improving the settings which I’ll get to. Testing, I did a Plex search, selected a few random episodes which is now with Transmission. While I do not know enough to know how well it all working, this is all much better than past setups and attempts. I am using a new version of Jackett w/a different IP.

sonarr kickass not working

#Sonarr kickass not working full

The sonarr trace logs dont seem to have captured a full search, there is what looks like the end on one, maybe, but the error points to getting no response from jacket (as if the ip address was wrong?)ĭo you have any anti-virus / web protection software on your mac that could be interfering? perhaps disable it temporarily to see if they start working ok? Im presuming the initial connectivity issues may have been due to an ip address change and youve catered for those already? or did jackett end up with 172.17.0.3 again? Youre also getting Resource temporarily unavailable on limetorrents so that indexer may be having its own (temporary) issues. Key may be persisted to storage in unencrypted form.īut it doesnt appear on more recent startups so the rebuild may have fixed those Its also generating this warning, which doesnt appear to be an issue but you may want to check on the jackett forums. Jacket having a jackett folder under config is a bit non standard but it seems thats how they set it up. These are probably enough to get me going, maybe not worth the time to chase after a few index problems at this stage as the states of getting Transmission (desktop) connected and then VPN (where I can still remote in) lie ahead. Success at adding a few more indexes to both Radarr and Sonarr now, and still failing on the others.

#Sonarr kickass not working manual

These two test, manual search are working, category codes are accurate…baffled. I was able to add those successful indexes to Radarr (yea!), and failed on those same two above. Try another (ExtraTorent) - tests, search all good… same error adding to Sonarr.Īlmost as if something changes somewhere along the line and prevents adding more? This was all in one session btw, adding three no problem then hitting the wall on number 4, and 5. Throws an error “No results were returned from your indexer, please check your settings.”

sonarr kickass not working

Go to add the forth (this one would be TorrentProject2), it tests fine, manual search fine. Successfully added a few indexers (YEA!! Amazing) Commands you have shared here have helped, so was able to go into shell of the new Jackett instance, get the ip, ensure the categories match etc. Started a completely fresh Jackett different directory, key etc.














Sonarr kickass not working