Can't access SAB from within LAN

[gooobery]

I've setup SAB and got it all working re downloads etc and can access it on the localhost but for some reason I can't access the server/webpage from a remote location within my LAN i.e. another PC. I've tested multiple solutions and so far nothing has worked. Things I have tried include:
1. Switching off the firewall on the machine where SAB is installed.
2. trying different combinations/variations of the address to the server IP e.g. http://[Server IP address]:8085/sabnzbd (note my SAB is installed to port 8085, not 8080 as what most people seem to think it installs to. SAB must have auto-configured it as I have my torrent client listening on port 8080 prior to installing SAB.
3. Trying a 3rd party mobile app to connect to the SAB server.
4. I do not think port forwarding is required in my router as that is more to do with accessing SAB from outside my LAN. I have sickbeard, couchpotato, plex etc all working and none of them requires port forwarding so I do not see any reason as to why SAB should require it.

So far nothing has worked. Like I said I can still access it without issue on the localhost where its installed but the site completely timesout/doesn't load when attempting to access it from another machine/device on the LAN.

Help!

[shypike]

First of all, you needs SABnzbd to listen to something else than localhost or 127.0.0.1
Set its host address in Config->General to 0.0.0.0
Also instruct the firewall to let SABnzbd trough on its designated port.

Second, if you want external access (the big bad internet),
you need to setup port-forwarding on your router.

[gooobery]

First of all, you needs SABnzbd to listen to something else than localhost or 127.0.0.1
Set its host address in Config->General to 0.0.0.0
Also instruct the firewall to let SABnzbd trough on its designated port.

Second, if you want external access (the big bad internet),
you need to setup port-forwarding on your router.

Thanks for the reply. I'll try playing around with the host address and see if that helps. Re port forwarding, as I said, I tried it with the firewall disabled I still had the same issue and I have no interest in accessing SAB from outside my LAN so I do not believe setting up port forwarding will be of any use here.

[gooobery]

Great! Setting the host address to 0.0.0.0 did the trick! Kind of makes sense as it means that it'll listen for all IP's on the network but it is strange that SAB works differently to couchpotato, plex and sickbeard as they're equivalent setting sets it as the localhost IP but still accepts incoming connections from other devices on the LAN.

[shypike]

SickBeard uses the same web framework as SABnzbd does.
So if they allow a host setting of localhost or 127.0.0.1 to listen
to other systems, they're cheating.
They must be opening a listening channel for other systems.
Which is pretty bad, because if you're using localhost or 127.0.0.1
you should trust the software not to listen to incoming external traffic.
If you know that to be a fact, you can decide not to use username/password protection.

[Benzima]

Pardon my ignorance but, what do you do after you change the host address from 127.0.0.1 to 0.0.0.0?

Thanxxx in advance.

[sander]

Pardon my ignorance but, what do you do after you change the host address from 127.0.0.1 to 0.0.0.0?

Thanxxx in advance.

Restart SABnzbd.

[goodtimes50]

Thought about starting a new thread, but since this is near the top and I have the same issue I'll just post here. The only difference is that none of the suggestions here work. I did a fresh install of the Anniversary Update in Win 10 and reinstalled SAB. I restored sabnzbd.ini from a backup (which was working fine) and I'm unable to access SAB from any other device on my LAN. I've tried setting the host to 127.0.0.1, 0.0.0.0. and the IP of the machine it's on. I've tried various (unused) ports, including 8080. I've set the "List of local network ranges" and left it blank. Windows firewall is set to allow SAB. Nothing works. Any other suggestions?

[sander]

Thought about starting a new thread, but since this is near the top and I have the same issue I'll just post here. The only difference is that none of the suggestions here work. I did a fresh install of the Anniversary Update in Win 10 and reinstalled SAB. I restored sabnzbd.ini from a backup (which was working fine) and I'm unable to access SAB from any other device on my LAN. I've tried setting the host to 127.0.0.1, 0.0.0.0. and the IP of the machine it's on. I've tried various (unused) ports, including 8080. I've set the "List of local network ranges" and left it blank. Windows firewall is set to allow SAB. Nothing works. Any other suggestions?

Start with the low-level basics:

Find PID (Process ID) of SABnzbd on your Windows:

Code: Select all

C:\>tasklist | find /i "sabnzbd"
SABnzbd.exe                   6264 Console                    1    36.176 kB

With that PID (in my case: 6264), find the listening host:

Code: Select all

C:\>netstat -aon | find "6264"
TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING       6264
TCP    [::]:8080              [::]:0                 LISTENING       6264

Report that here

[goodtimes50]

Okay, here you go...

Code: Select all

C:\WINDOWS\system32>tasklist | find /i "sabnzbd"
SABnzbd-helper.exe            4196 Services                   0      2,172 K
SABnzbd-service.exe          12632 Services                   0     21,204 K

C:\WINDOWS\system32>netstat -aon | find "12632"
  TCP    0.0.0.0:8085           0.0.0.0:0              LISTENING       12632
  TCP    192.168.xx.xx:8085       192.168.xx.xx:57917      ESTABLISHED     12632
  TCP    192.168.xx.xx:8085       192.168.xx.xx:59620      ESTABLISHED     12632

[sander]

So SABnzbd is running on port 8085. Did you try that?

Why did you post "192.168.xx.xx"; those are local LAN IP addresses, so not privacy or security sensitive. Now I can't see if that is another system on your LAN.

Wait, I'll give you proof how non-privacy-sensitive those are: here are mine:

Code: Select all

C:\>netstat -aon | find "4204"
TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING       4204
TCP    127.0.0.1:8080         127.0.0.1:54910        ESTABLISHED     4204
TCP    127.0.0.1:8080         127.0.0.1:54919        ESTABLISHED     4204
TCP    127.0.0.1:54908        127.0.0.1:5354         ESTABLISHED     4204
TCP    192.168.1.235:8080     192.168.1.205:57158    ESTABLISHED     4204
TCP    192.168.1.235:8080     192.168.1.205:57159    ESTABLISHED     4204
TCP    192.168.1.235:8080     192.168.1.205:57160    ESTABLISHED     4204
TCP    192.168.1.235:8080     192.168.1.205:57161    ESTABLISHED     4204
TCP    192.168.1.235:8080     192.168.1.205:57162    ESTABLISHED     4204
TCP    192.168.1.235:8080     192.168.1.205:57163    ESTABLISHED     4204
TCP    [::]:8080              [::]:0                 LISTENING       4204

[goodtimes50]

So SABnzbd is running on port 8085. Did you try that?

Why did you post "192.168.xx.xx"; those are local LAN IP addresses, so not privacy or security sensitive. Now I can't see if that is another system on your LAN.

Wait, I'll give you proof how non-privacy-sensitive those are: here are mine:
[/code]

Haha, fair enough. Just habit I suppose. Anyway, they're both 192.168.0.5, which is the machine SAB is running on. My guess is that they are the web interface I had up in my browser and the SabConnect++ Chrome extension.

[sander]

OK, so you use http://192.168.0.5:8085/ to access SABnzbd?

Does that work with that URL from the machine SABnzbd is running on?
Does that work with that URL from another machine on your LAN ?

[goodtimes50]

OK, so you use http://192.168.0.5:8085/ to access SABnzbd?

Correct.

Does that work with that URL from the machine SABnzbd is running on?

Yes.

Does that work with that URL from another machine on your LAN ?

No. Using 192.168.0.5:XXXX for services like Sonarr and CouchPotato works fine though.

[sander]

OK, I would do this: temporarily de-install and remove your firewall, and reboot. Then try again.