Web interface unavailable

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
houdini2286
Newbie
Newbie
Posts: 5
Joined: August 7th, 2012, 11:58 pm

Web interface unavailable

Post by houdini2286 »

I can no longer reach SABnzbd outside my home. I know what you're thinking - it's a router issue. I really don't think it is. I've factory reset the thing and I'm able to open up ports for all the other various services I'm running, except SABnzbd, CouchPotato and SickBeard. Other services work fine - Headphones, Calibre, Subsonic and more. I can reach SABnzbd, but only when I use "localhost" in the URL.

When I restart SABnzbd, I get:

"SABnzbd needs a valid host address for its internal web server. You have specified an invalid address."

"uname -n" is returning mydomain.dyndns.org and I can ping it just fine.

I'm using OSX Mountain Lion. If anyone has any ideas, they'd be much appreciated. I'm left scratching my head over this. Everything was working fine for a long time using this setup.

Debug logs:

Code: Select all

2012-08-08 00:20:22,104::INFO::[SABnzbd:1468] Starting web-interface on mydomain.dyndns.org:27078
2012-08-08 00:20:22,107::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus STARTING
2012-08-08 00:20:22,110::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Started monitor thread '_TimeoutMonitor'.
2012-08-08 00:20:22,114::ERROR::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
  File "cherrypy/process/servers.pyc", line 75, in _start_http_thread
  File "cherrypy/wsgiserver/__init__.pyc", line 1644, in start
error: [Errno 49] Can't assign requested address

2012-08-08 00:20:22,114::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus STOPPING
2012-08-08 00:20:22,114::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('mydomain.dyndns.org', 27078)) already shut down
2012-08-08 00:20:22,118::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Stopped thread '_TimeoutMonitor'.
2012-08-08 00:20:22,119::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus STOPPED
2012-08-08 00:20:22,119::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus EXITING
2012-08-08 00:20:22,119::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus EXITED
2012-08-08 00:20:22,214::ERROR::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x107227d50>>
Traceback (most recent call last):
  File "cherrypy/process/wspbus.pyc", line 147, in publish
  File "cherrypy/_cpserver.pyc", line 90, in start
  File "cherrypy/process/servers.pyc", line 62, in start
  File "cherrypy/process/servers.pyc", line 97, in wait
error: [Errno 49] Can't assign requested address

2012-08-08 00:20:22,214::ERROR::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Shutting down due to error in start listener:
Traceback (most recent call last):
  File "cherrypy/process/wspbus.pyc", line 184, in start
  File "cherrypy/process/wspbus.pyc", line 147, in publish
  File "cherrypy/_cpserver.pyc", line 90, in start
  File "cherrypy/process/servers.pyc", line 62, in start
  File "cherrypy/process/servers.pyc", line 97, in wait
error: [Errno 49] Can't assign requested address

2012-08-08 00:20:22,215::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus STOPPING
2012-08-08 00:20:22,215::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('mydomain.dyndns.org', 27078)) already shut down
2012-08-08 00:20:22,215::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE No thread running for _TimeoutMonitor.
2012-08-08 00:20:22,215::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus STOPPED
2012-08-08 00:20:22,215::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus EXITING
2012-08-08 00:20:22,215::INFO::[_cplogging:55] [08/Aug/2012:00:20:22] ENGINE Bus EXITED
2012-08-08 00:20:22,216::ERROR::[SABnzbd:1483] Failed to start web-interface: 
Traceback (most recent call last):
  File "/Applications/SABnzbd.app/Contents/Resources/SABnzbd.py", line 1475, in main
  File "cherrypy/process/wspbus.pyc", line 184, in start
  File "cherrypy/process/wspbus.pyc", line 147, in publish
  File "cherrypy/_cpserver.pyc", line 90, in start
  File "cherrypy/process/servers.pyc", line 62, in start
  File "cherrypy/process/servers.pyc", line 97, in wait
error: [Errno 49] Can't assign requested address
2012-08-08 00:20:22,216::ERROR::[SABnzbd:302] Failed to start web-interface : [Errno 49] Can't assign requested address
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Web interface unavailable

Post by shypike »

If "uname -n" delivers an internet address, your DNS is wrong.
mydomain.dyndns.org is not your computer's address, but your router's.

Instead find out what the internel network address of your system is and use that.
houdini2286
Newbie
Newbie
Posts: 5
Joined: August 7th, 2012, 11:58 pm

Re: Web interface unavailable

Post by houdini2286 »

But, even if I change the hostname to "localhost" or "127.0.0.1", the issue remains. I can't access remotely even though I'm forwarding the port. When I test the port forwarding it's failing but I'm confident I'm setting it up right on my router because like I said, I've had this working great for over a year and all of these other services are forwarding just fine.

I'm thinking it has something to do with the upgrade to 0.7.3, the upgrade to Mountain Lion or both?
houdini2286
Newbie
Newbie
Posts: 5
Joined: August 7th, 2012, 11:58 pm

Re: Web interface unavailable

Post by houdini2286 »

Oh I see... if I use the local network IP (192.168.1.80), it seems to be working.

Thanks for your help. Hopefully this solves it. Strange that it would have worked OK before...
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Web interface unavailable

Post by shypike »

Normally 0.0.0.0 should work, provided 'uname -n' delivers a name that resolves to the local IP address.
This is not the case for your system.
127.0.0.1 will never support external access, it's called "localhost" for a reason :)
spyder
Newbie
Newbie
Posts: 2
Joined: August 11th, 2012, 10:53 pm

Re: Web interface unavailable

Post by spyder »

I just had the same problem - it's not 0.7.3 specific, it's something at the OS level. This morning I upgraded my OS X 10.6 media server from SABNzbd 0.6.15 to 0.7.3, and then upgraded from OS X 10.6 to OS X 10.8. Only after the OS upgrade did it break.

Turning off ipv6 as suggested does work around the problem, but I'm actually on a valid ipv6 network so I wasn't happy leaving it like that.

I tracked it down to the daemon option. I am using a LaunchDaemon config described in an old forum post, and added -d because LaunchDaemons load behind the login window (I leave the machine logged out most of the time).

Removing -d allows SABNzbd to load with ipv6 support, but only while logged in. When launching on boot (or via ssh when logged out) even without -d it won't start properly until I disable ipv6.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Web interface unavailable

Post by shypike »

You can disable IPv6 just for SABnzbd (or rather stop it trying to serve on ::1).
This is done by adding --no_ipv6 as a parameter when starting it from Terminal, once.
spyder
Newbie
Newbie
Posts: 2
Joined: August 11th, 2012, 10:53 pm

Re: Web interface unavailable

Post by spyder »

yes, that's how I got it working, but disabling ipv6 seems like a pretty silly requirement for running in daemon mode (even if daemon mode is an unusual thing to do on OS X).

[edit] Just noticed the bit on the howto page about sabnzbd as a daemon not working. Odd that it worked perfectly in daemon mode with ipv6 under 10.6, but with 10.8 it's broken.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Web interface unavailable

Post by shypike »

spyder wrote:but with 10.8 it's broken.
No, it isn't. It's broken on your system, not on mine.
Now if I only knew what causes the difference in behavior...
Post Reply