SABnzbd Forums

Hello,

I have an Livebox-Fast-3202 router, with two computers. The local IP's are 192.168.1.11 (with running sabnzbd) and 192.168.1.10 (just a laptop). I'm trying to set up sabnzbd accessible world wide but it fails.

I'm using port 50000. This one is open (checked with canyouseemee.org). When I fill in @ "host" my local ip (192.168.1.11) or when I leave it empty I can acces sabnzbd on both my desktop and laptop but not on any other computer. When I fill in 0.0.0.0 or my external IP I can't visit sabnzbd on my desktop and neither on my laptop.

I'm sure the port is open, so what is the problem? I'm using Vista SP1 with SABnzbd+ 0.4.0 RC4

Thank you in advance. 

Check the rules in the Wiki:

"localhost", obvious isn't it?
"", host ip only (so not localhost)
"0.0.0.0", localhost + host-ip

Host-ip being 192.168.1.11 in your case.
Given your problem, I' would just hardcode 192.168.1.11 as the host address.

More important, have you set up port redirection on your router?
You need to tell the router that any incoming traffic for port 50000 needs to go to 192.168.1.11.
It won't do this by itself.

Aside from that, I would be careful by putting SABnzbd on the Internet, only protected by a username and password.
You do have a username and password set?

shypike wrote: Check the rules in the Wiki:

"localhost", obvious isn't it?
"", host ip only (so not localhost)
"0.0.0.0", localhost + host-ip

Host-ip being 192.168.1.11 in your case.
Given your problem, I' would just hardcode 192.168.1.11 as the host address.

More important, have you set up port redirection on your router?
You need to tell the router that any incoming traffic for port 50000 needs to go to 192.168.1.11.
It won't do this by itself.

Aside from that, I would be careful by putting SABnzbd on the Internet, only protected by a username and password.
You do have a username and password set?

Yes, I have set username and a password. As I said, when I leave host emty or filled in with "192.168.1.11" I can acces the WebGui with my laptop or the PC itself. But when I fill in my external IP or "0.0.0.0" I can´t acces it with neither my desktop nor my laptop.

So I have tried
host : "192.168.1.11" ----> accessible with desktop and laptop, not with any other PC
host : "" ----> accessible with desktop and laptop, not with any other PC
host : "0.0.0.0." ----> not accessible
host : "externalIP" ----> not accessible
host : "localhost" ----> accessible with desktop

According canyouseeme.org my port is forwarding correctly

If the blank host and localip host work on your laptop, then they should work fine externally if you have your network set up to forward the port to your desktop machine.

If it does not work, then it will be a network issue and not sabnzbd.

Simon,

ExternalIP isn't going to work.
As far as your PC knows , there is no externalIP because it's owned by the router.
ONLY 192.168.1.11 can ever work in your situation.

Given that 0.0.0.0 and "" are not working, means that there is something fishy in your
network setup, which makes that SABnzbd cannot determine the PC's IP address (192.168.1.11).
Too bad, but the work-around is to specify 192.168.1.11 explicitly.

I'm still not comfortable with your router.
Have you actually set up port-redirection for port 50000 to go to 192.168.1.11:50000 ?
How did you do that on the router?

Here is a screenshot of my setup.





I tried something in the last screen a hour ago, it still didn´t work.


By the way, I tried port 80 instead of 50000 but canyouseeme.org told me 80 was still closed ... strange 

Port 80 is likely to be blocked by your ISP.
They don't want you to run a webserver.

Don't know your router, but the first screen looks OK to me.
The second screem I don't understand.
Does Rule 11 have precedence over the other rules?
I don't understand the rules for the local addresses.
How does it relate to the other screen?

I don't understand it either. Normally I forward my ports using the first screen but today when I was looking for a solution I found the second screen by going to the "advanced menu" and then Firewall --> NAT --> Policy Based NAT and tried a few things.