0.5.0 RC3 No access to web interface - Ubuntu

[s1nglebarrel]

Not sure whats going on but was running the beta 6 with out issue and then just udated to RC3 and now I can no longer log into the web interface.

Running on Ubuntu 8.04 LTS was using SSL ports 9090. I have tried all the combinations I can think of but no dice on getting the web interface working.

Any thoughts or suggestions would be welcome!

**Edited**
Ok some more info. if I manually run sabnzbdplus I get the setup wizard. However if I try and launch sabnzbdplus as a daemon I get the following error in the error log.

Code: Select all

Exception in thread HTTPServer Thread-10:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.5/threading.py", line 446, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/share/sabnzbdplus/cherrypy/process/servers.py", line 75, in _start_http_thread
    self.httpserver.start()
  File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1629, in start
    raise socket.error, msg
error: (99, 'Cannot assign requested address')

Not sure what "cannot assign requested address' means s I am not sure what "address" it is trying to request.

Also getting this in the standard log

Code: Select all

2010-01-22 13:25:46,854::ERROR::[misc:453] You have no permisson to use port 8181

[young-einstein]

I had this problem as well when I upgraded to RC3.

Long story short, I found out that the only way I could access the web interface was to use the machines proper hostname, not just 'localhost' like I'd always done previously.

EG:  http://:8080/sabnzbd

Once I changed this, everything worked perfectly again.

If you don't know it already, you can find your machines hostname by opening a terminal window and just typing "hostname" [no quotes].

Let me know if that helps you at all ...

--David

[shypike]

localhost translates to an IPV6 address on more recent systems.
Ubuntu 9.10 translates the hostname to 127.0.0.1 (unlike previous releases).
In short: it's a bloody mess, each Linux distro does as it pleases.

[s1nglebarrel]

Ok check this out. If I manually launch sabnzbd with the following command logged in as root sabnzbd performs just like it did before the update

sabnzbdplus -f /etc/sabnzbd/sabnzbd.ini

The page launches fine and I am able to access the page just using my domain name with the proper 9090 port at the end. So I guess long story short how come when the application is launched via init.d it fails to run? I would assume it would be launching the same or similar command that I just manually type in.

[shypike]

Please discuss this with the package maintainer, in our Debian/Ubuntu board.

[s1nglebarrel]

Please discuss this with the package maintainer, in our Debian/Ubuntu board.

Will do! Thanks for the fast response