Page 1 of 1

Logging on to 192 ...

Posted: December 30th, 2014, 1:05 am
by bugoy8
Hi guys

Hoping someone could help. Moved laptops and moved the sabnzdb app. I migrated to ini file to bring across the config. Done this a number of times before without any issues.

However this time around I cannot logon from a different pc using the IP. Normally I just logon via 192.xxx.xxx.xxx:8080. Now nothing happens when I go to this address.

Any ideas why? Thanks

Re: Logging on to 192 ...

Posted: December 30th, 2014, 2:13 am
by sander
Different laptop, so different IP?

So: what is the IP address of the laptop running SABnzbd? On Windows you can find out with "ipconfig", on Linux/OSX with "ifconfig"

Re: Logging on to 192 ...

Posted: December 30th, 2014, 3:02 am
by bugoy8
Yup I'm using the static IP of the new laptop. 192.168.1.xx:8080

Nothing happens when I bring that up

Sickbeard on the otherhand, works with no issues. Has to be some config that I've missed

Re: Logging on to 192 ...

Posted: December 30th, 2014, 3:21 am
by sander
FWIW: no need to keep your private LAN address secret: it's unroutable and unreachable from Internet. Here's mine: 192.168.8.168.

Anyway: In SABnzbd: Config -> General: what is filled out at "SABnzbd Host"?

Re: Logging on to 192 ...

Posted: December 30th, 2014, 4:19 am
by bugoy8
Yeah gathered that. I know it internal. Host is 0.0.0.0. Always been the case

I tried changing to the IP - 192.168.1.94 and still nothing.

What should be the host be?

Re: Logging on to 192 ...

Posted: December 30th, 2014, 5:53 am
by shypike
Are you sure the IP is still valid?
Maybe your router decided to change the address assignment.
Do you have multiple interfaces, like Wifi and wired?

Re: Logging on to 192 ...

Posted: December 30th, 2014, 6:21 am
by bugoy8
Yeah the IP is valid. In fact I assigned this myself. Had it been invalid, Sickbeard wouldnt work as well right?

I changed it to obtain IP automatically and used the IP assigned. Same result - Sickbeard works and Sabnzdb does not.

I do have multiple interfaces ... Should I check something here? I'm using wired for the network connection and I'm using that IP

EDIT *** just removed and reinstalled it. Used the same ini file for config. No luck Same results. This is so frustrating

Re: Logging on to 192 ...

Posted: December 30th, 2014, 6:41 am
by shypike
If you're setting a correct real IP address, SABnzbd will use that.
It may have some issues with multiple interfaces, if it needs to find out the IP by itself.
You're sure the port numbers of SABnzbd and SickBeard don't clash?
BTW: which operating system are you using?

Re: Logging on to 192 ...

Posted: December 30th, 2014, 7:04 am
by bugoy8
Win7 64-bit

Sickbeard port is 8081
Sabnzbd port is 8080

Shouldnt be a clash there

if I call 192.168.1.94:8080 from the local machine it works. So it knows the IP

EDIT *** just tried on another machine where the app used to be installed. That one works when you call the IP ...

Gotta be something on this laptop. Some config somewhere ...

Re: Logging on to 192 ...

Posted: December 30th, 2014, 8:28 am
by sander
Is there a firewall running on that new laptop? What happens when you stop Sickbeard, and run SABnzbd on port 8081?

Furthermore: ... logging! Set Logging to +debug, restart SABnzbd and check the logging for these lines:

$ cat ~/.sabnzbd/logs/sabnzbd.log | grep -i -e "my ip" -e serving

Code: Select all

2014-12-30 14:14:27,383::DEBUG::[sabnzbdplus:1271] My IPv4 address = 192.168.1.113
2014-12-30 14:14:27,400::DEBUG::[sabnzbdplus:1280] My IPv6 address = 2002:5a::1be

2014-12-30 14:14:27,656::INFO::[_cplogging:55] [30/Dec/2014:14:14:27] ENGINE Serving on 0.0.0.0:8080
2014-12-30 14:14:27,758::INFO::[_cplogging:55] [30/Dec/2014:14:14:27] ENGINE Serving on 0.0.0.0:9090

Re: Logging on to 192 ...

Posted: December 30th, 2014, 4:41 pm
by bugoy8
sander wrote:Is there a firewall running on that new laptop?
sander ... that's it! It's the Windows firewall that was blocking it! ;D

Thanks so much for pointing that out. All working now!

When setting it up, must have just clicked through the network settings and made my internal network public!

Awesome stuff ... thanks guys!