SABnzbd Forums

I had Sabnzbd working perfect for a couple of weeks, but all of a sudden I'm not longer able to connect when trying to through http://localhost:8081/sabnzbd/  (had it installed on port 8081).

Not sure where to start trouble shooting. Simply getting an Unable to Connect message on Firefox and something similar on IE.

Any suggestions?

Try this.  Open sabnzbd.ini.  Search for the line "host =".  Change it to "host = 0.0.0.0".  Save and restart program.  If this fixes your problem please let me know what the old value was.

Thanks for the reply.

There was nothing in the host field, just two "", I changed that to 0.0.0.0, and that did not correct the problem.

Any other suggestions?

Which OS do you use?

Using Windows XP

Odd.
SABnzbd assumes that when it asks the OS for the hostname
it will get a name that will resolve to the system's IP address.
Some systems (like all Ubuntu Linux 9.10) and some oddly
configured others (yours?) give a name that resolves to 127.0.0.1 (localhost).

What is the hostname of your system and what
show when you type this in a command prompt? (substitute hostname by your system's hostname).

Thanks for the reply.

The hostname of my computer is Dell-9150 and when I ping that hostname I get the following:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mike Jones>ping dell-9150

Pinging dell-9150 [192.168.1.109] with 32 bytes of data:

Reply from 192.168.1.109: bytes=32 time

Try this address:
http://[::1]:8081/sabnzbd/

It worked for me. localhost wasnt working for me in firefox, but i could access it through IE.

I'm running Ubuntu [9.10], and I've always used http://localhost:8080/sabnzbd to access SABnzbd, and that's never given me a problem.

When I upgraded to 0.5.0 RC3 though, this suddenly stopped working and I had no idea what was going on.  It took me a few minutes to work out that for some reason it was refusing to load using the 'localhost' address, and I had to use the machines DNS name instead.  As soon as I changed that, everything started working fine again.

My interface name has always just been left blank ...

localhost is ambiguous on  many systems.
Sometimes it resolves to 127.0.0.1 and sometimes to [::1] (IPV6).

had this issue, sabnzbd installed on a distant ubuntu server, after an aptitude upgrade i was only able to connect throught localhost (the server itself), unable to acces the web interface by its ip or hostname from a remote client.

First thing, i checked the SABnzbd.ini and the host was host =""
previously it was like host = XXX.XXX.XXX.XXX
I set it back, saved and restart daemon, and surprise the host parameter was setback to host=""

So after some chmod tries i checked  /etc/default/sabnzbdplus and host parameter was also blank so i put back the ip here  save and restart and it now works like a charm.

Ubuntu has changed the way they handle localhost and the hostname
a couple of times in the last few years.
I've lost track.

maxmax wrote:So after some chmod tries i checked  /etc/default/sabnzbdplus and host parameter was also blank

Code: Select all

# [optional] hostname/ip and port number to listen on:
HOST=
PORT=9200

The rc3 package has a minor change in the behaviour of the init script. Previously, it would only use the HOST and PORT settings in /etc/default/sabnzbdplus if both were set; now, setting just one of 'm also takes effect. As a result, if you had only the PORT set (which had no effect at all), it will now start using that as --server :port which is where the hostname guessing game begins. Unfortunately, Ubuntu isn't very steadfast in how it handles that. Anyway, you figured out the correct solution already

dbznbas wrote: Try this address:
http://[::1]:8081/sabnzbd/

It worked for me. localhost wasnt working for me in firefox, but i could access it through IE.

Thanks for the suggestion, just tried that and still not working on either FF or IE. Pretty discouraging because I really started to like this program, but might have to go back to Newsleecher instead.

Hmmmm

@ Touchdown :

What happens when you type : http://192.168.1.109:8081/sabnzbd/

As when your IP of PC is : 192.168.1.109 , and you are really running sabnzbd+ op port 8081 .. it should all work