IP Change on WHS causes no access to SABnzbd Manager

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
andilatte
Newbie
Newbie
Posts: 2
Joined: February 19th, 2011, 3:58 pm

IP Change on WHS causes no access to SABnzbd Manager

Post by andilatte »

I am using SABnzbd Manager which is an add-in for Windows Home Server. It runs quite well, but I have had to change my server IP from 192.168.1.5 to 192.168.2.5 (or any other I have tried) to get VPN working.

Now I have the problem that after changing the IP I can not access the interface on WHS console or via web interface on https://myWHSname:9090/sabnzbd/ or https://WHSIP:9090/sabnzbd/
As soon as I change back the IP of my WHS to 192.168.1.5 I have access as usual.

I tried to uninstall the add-in, change IP and reinstall it, but still the same error occurs. I had change "host = " entry in sabnzbd.ini to the new IP, but without any effect on the error.

I am running out of ideas and your help is very appreciated.
andilatte
Newbie
Newbie
Posts: 2
Joined: February 19th, 2011, 3:58 pm

Re: IP Change on WHS causes no access to SABnzbd Manager

Post by andilatte »

Unfortunately changing sabnzbd host = 0.0.0.0 // 127.0.0.1 or [::1] or localhost // or leave it empty does not work for the Add-In. I still got the error message "The operation timed out when attempting to contact 192.168.1.5"

When using the Web UI in the browser on my local maschine I still have access to sabnzbd on my Windows Home Server. I guess it is a problem with the Add-In or the interface of the Add-In itself.
Post Reply