I am runnig Sabnzbd and prowlarr on my nas in docker but I cannot get conect sabnzb to prowlarr I keep getting this erroe. Test was aborted due to an error: Unable to connect to SABnzbd, One or more errors occurred. (Connection refused) (127.0.0.1:8080). dose anyone know how I could sort it please.
5 replies
Chris wrote:
Got it — this is an automatic acknowledgment from Chris, your AI support representative. Your post is in the support queue, and we’ll get to it as soon as we can. Legend members receive priority replies. If you’d like faster support while helping fund the project’s goals and continued development, consider becoming a Legend backer. <!-- chris-support-queue-ack:v1 --
Chris wrote:
That Connection refused error on 127.0.0.1:8080 is typically because the two apps are in separate Docker containers and can't reach each other on localhost.\n\nBefore we dig deeper: are you running these in SparkBox, or in standalone Docker on your NAS?\n\nIf it's SparkBox, SABnzbd should be reachable from Prowlarr at http://sb-sabnzbd:8080 (not localhost). The same applies to any arr app — they all live on the same internal network (sbproxy) and communicate by container name.\n\nIf it's standalone Docker, you'll need to make sure both containers are on the same custom Docker network (not the default bridge). Try: docker network ls to see what networks exist, then check which one has both containers — reply with those results.\n\nLet me know which setup you have and what the network check shows, and we can walk through the right connection string or network fix.
ABL wrote:
I am running them in SparkBox.
Chris wrote:
Thanks for confirming. Connection-refused usually happens when Prowlarr can't reach SABnzbd's container name. In SparkBox, use http://sb-sabnzbd:8080 (not localhost). First: what's your SparkBox version? Run sparkbox -v. There was a fix in v1.6.679 for SABnzbd category creation issues.
Chris wrote:
ABL — let me verify something: what version of SparkBox are you running? Run sudo sparkbox version and let me know what it shows. The reason I'm asking: there was a fix for SABnzbd category creation in v1.6.679 that addressed exactly this connection-refused symptom. If you are on an older version, upgrading will likely resolve it.