Connection fails to sabnzbd

Help & Support
1

Sonarr version (exact version): 2.0.0.4230
Mono version (if Sonarr is not running on Windows): 4.4.1 (Nightly 4.4.1.0/4747417 Wed Jun 22 11:14:49 UTC 2016)
OS: Ubuntu 14.04.4 LTS

Debug logs (posted to hastebin or similar):
sonarr log
http://hastebin.com/amiwedumej.tex

Description of issue:
recently updated to some latest versions of sabnzbd (1.1.0RC1 [aa12e21]) and sonarr, and probably mono. Couchpotato still connects to sabnzbd no problemo, but sonarr has quit behaving. The error logs don’t seem to tell me much. Thanks!

sabnzbd settings

816×883

sonarr settings

798×793

2

The connection was refused, which usually means something blocked it, such as a firewall or nothing was listening on that port so the OS refused it. Based on the screenshots it everything else looks correct.

3

Looks like something is listening there via netstat.

root@mimi:/var/log# netstat -ntlup | grep 8080
tcp        0      0 192.168.11.52:8080      0.0.0.0:*               LISTEN      12342/python

and listening via ss

root@mimi:/var/log# ss -tnlp | grep :8080
LISTEN     0      5             192.168.11.52:8080                     *:*      users: (("python",12342,5))

And the firewall is not running

root@mimi:/var/log# ufw status
Status: inactive

Telnet to the local host:

telnet> open localhost 8080
Trying ::1...
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
telnet>

But I can connect to my plex server port

telnet> open localhost 32400
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
^]
telnet>
4

Got the actual TRACE error log for you. I tried changing the port to 8083. Still, couchpotato connects no problem.

http://hastebin.com/iciyekuvol.tex

5

That won’t work if SAB is only listening on the private IP. Any difference if you tell SAB to listen on all IPs (0.0.0.0)?

Are SAB and Sonarr on the same machine?
Are SAB and CP on the same machine?

6

Now we’re getting somewhere! Moving sabnzbd General > SABNZBD Host > 0.0.0.0, connection succeeds.

2016-07-13 08:05:24,167::DEBUG::[interface:420] API-call from 127.0.0.1 [Sonarr/2.0.0.4230 (Linux 3.13)] {'output': 'json', 'apikey': '7a1c3xxxxxxxxxxxxxxxxxxxxxxxxxx','mode': 'version'}
2016-07-13 08:05:24,170::DEBUG::[interface:420] API-call from 127.0.0.1 [Sonarr/2.0.0.4230 (Linux 3.13)] {'output': 'json', 'apikey': '7a1c3xxxxxxxxxxxxxxxxxxxxxxxxxx','mode': 'get_config'}
2016-07-13 08:05:24,178::DEBUG::[interface:420] API-call from 127.0.0.1 [Sonarr/2.0.0.4230 (Linux 3.13)] {'output': 'json', 'apikey': '7a1c3xxxxxxxxxxxxxxxxxxxxxxxxxx','mode': 'get_config'}
2016-07-13 08:05:24,190::DEBUG::[interface:420] API-call from 127.0.0.1 [Sonarr/2.0.0.4230 (Linux 3.13)] {'output': 'json', 'apikey': '7a1c3xxxxxxxxxxxxxxxxxxxxxxxxxx','mode': 'get_config'}
2016-07-13 08:05:24,201::DEBUG::[interface:420] API-call from 127.0.0.1 [Sonarr/2.0.0.4230 (Linux 3.13)] {'start': '0', 'apikey': '7a1c3xxxxxxxxxxxxxxxxxxxxxxxxxx', 'limit':'1', 'mode': 'queue', 'output': 'json'}`

from the sabnzbd.log, while set on DEBUG level.

SAB and Sonarr are on the same machine.
SAB and CP are also on the same machine.

Can I just leave sabnzbd on 0.0.0.0? Or do you think that will screw up other things?

7

You can, it will allow connecting from other IP addresses, but no need to lock it down if you don’t have a reason to.

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.