SABnzbd Forums

Hello,

I have a dynamic DNS setup and had SAB setup to listen on that address, working great for several months.

Suddenly I was unable to reach my SAB page, so I checked all my settings, closed SAB and relaunched it.

Still no luck, so I decided to edit the ini file and enable the 'Launch Web Browser on Startup' option.

Sure enough it launched, but the ip address for the page was now 192.168.187.1 which does not exist anywhere on my home network? That ip address is also not reflected anywhere in the ini file.

I tried renaming my ini file so that SAB would create a new one, and then changed the address to my dynamic DNS address, but it still wants to redirect to 192.168.187.1

Any ideas? It does work, but is very odd.

-cheers

jp22382 wrote: the ip address for the page was now 192.168.187.1 which does not exist anywhere on my home network?

How are you checking this? It sounds like the internal ip changed on the computer running sabnzbd.

If on windows:
Start>Run type "cmd"
type "ipconfig /all" and look for the ip address of your Local Area Connection.

Aren't you mixing up external/public and internal/private IP addresses?

DynDNS is used for your your external/public IP address. Using that DynDNS-name or public IP address will only lead you to the front door of your DSL/cable modem (or the device that does PPPoX), not to devices on your LAN.

192.168.x.y is an internal/private IP address, and will not be handled by DynDNS.

To connect your external/public DynDNS address & port to your internal IP address (on which SABnzbd is running) you should set up port forwarding. See http://portforward.com/routers.htm And yes, if your internal IP address (assigned by DHCP) changes, you have to handle that in the port forwarding.

And: SABnzbd doesn't need to know it's IP addrss in the sabnzbd.ini. Just fill out 0.0.0.0 to make SAB listen to requests from your LAN.

Ok, I just figured it out.

I had just installed VMWare recently, and one of the virtual ethernet connections was tripping things up.

The IP address on the machine hosting SAB is 192.168.0.100 but somehow 192.168.187.1 was being picked up from one of the VMWare connections.

I disabled the extra ethernet connection and things are back to normal.

That was really weird.

Sorry I should have included more info initially, I have port forwarding configured, firewall rules, all that.

My setup has been working for several months, able to access SAB from outside my network, so I was highly confused as to what was going on.

Thanks for taking a look!