
- #Sonarr connection refused how to
- #Sonarr connection refused manual
- #Sonarr connection refused windows


#Sonarr connection refused how to
Why would Sonarr ask you to enter an API key, if it already has its own in the Security settings?Īctually, here are the instructions directly on Jackett w/instructions on how to add to Sonarr. One of the key tutorial’s I was following had you take the Jackett api and use it for Sonarr. “Unable to connect to indexer, check the log for more details.” ~ sometimes experiment with the Categories per the selected indexer to match.
#Sonarr connection refused manual
Inside Jackett, indexes work, tests work, manual searches work. Mono version (if Sonarr is not running on Windows): 5.20.1.34 Thank you for the link to the discord docker support chat - I will post something there too in a hope its something someone's come across before.Followed many a tutorial, posts, instructions and keep hitting the wall at this same spot. and probably some other ridiculous variations as a 'maybe this'll work.' attempt lol. (and other direct links from the button on jackett) However I still get the exact same problem when trying to add indexes to Sonarr. This connects, and starting up a CLI and running curl -s returns my WAN IP as expected. (in my case, Jackett through Deluge) - by the looks of what i've read there, I've done the right thing and my connection seems fine and set up as it should - I amended my connection string to the below:ĭocker run -name=jackett -net=container:delugevpn -p 9117:9117 -v $/jackett/downloads:/downloads-e PUID=1000 -e PGID=1000 -e TZ=Europe/London -e AUTO_UPDATE=true -restart unless-stopped linuxserver/jackett Morning guys - as an - I read through your links and both were really helpful re using a VPN'd container to channel traffic for another container. Trying to add that index list to Sonarr is where I get stuck and get hit with this:Ĭhecking the log from Docker gives me this: I can access Jacket from and add indexers also fine. I have tested their IP returns from the CLI and they seem fine.

Jackett container is using my Deluge network for VPN (without doing this my indexes fail their tests as my ISP blocks them) - set up with the below powershell command:ĭocker run -name=jackett -net=container:delugevpn -e PUID=1000 -e PGID=1000 -e TZ=Europe/London -e AUTO_UPDATE=true -restart unless-stopped linuxserver/jackettĪnd I mapped port 9117 in the deluge container. I've gone through all other reports of this error I can find and can't get past this.

I'm new to this whole thing but trying to learn.
#Sonarr connection refused windows
I'm running docker on a windows OS and trying to hook sonarr into jackett but I keep getting the error 'Unable to connect to indexer, check the log for more details'.
