jasonmicron
Dabbler
- Joined
- Oct 24, 2017
- Messages
- 15
I've installed via TrueCharts sabnzbd, sonarr and deluge.
Sonarr and deluge talk just fine when assigning deluge as a download client and using this as the hostname in Sonarr for deluge:
deluge.ix-deluge.svc.cluster.local
Sabnzbd is a different story. Again, with @truecharts and their app, using this hostname I get "connection refused". Which means of course that it FOUND the container but the container refused to respond, which is normally a firewall thing:
sabnzbd.ix-sabnzbd.svc.cluster.local
I can pull up the web GUI for sabnzbd just fine. It all works. I've tried all combinations of using the API key possible (but I think it is being denied before the API key can even be sent). I can ping it using sabnzbd.ix-sabnzbd.svc.cluster.local from the Sonarr container. Not sure what I can check next. Using default ports. Any advice?
Sonarr and deluge talk just fine when assigning deluge as a download client and using this as the hostname in Sonarr for deluge:
deluge.ix-deluge.svc.cluster.local
Sabnzbd is a different story. Again, with @truecharts and their app, using this hostname I get "connection refused". Which means of course that it FOUND the container but the container refused to respond, which is normally a firewall thing:
sabnzbd.ix-sabnzbd.svc.cluster.local
I can pull up the web GUI for sabnzbd just fine. It all works. I've tried all combinations of using the API key possible (but I think it is being denied before the API key can even be sent). I can ping it using sabnzbd.ix-sabnzbd.svc.cluster.local from the Sonarr container. Not sure what I can check next. Using default ports. Any advice?
Last edited: