http://localhost:8080/sabnzbd/ not working after update

[Bubby]

Hey guys

Im a bit of a mac & sabnzb noob.

I running OSX Snow Leopard 10.6.4 & SABNZB 5.0.3 & Firefox 3.6.8.

I have just upgraded to SAB 5.0.3 from 5.0.2. I am having problems getting the page at http://localhost:8080/sabnzbd/ to display.  Since I have upgraded the page will no longer display. I have no problem downloading, I just cant display the page. I get "unable to connect, Firefox can't establish a connection to the server at localhost:8080 instead.

I had no problem displaying the page 10 minutes ago before I upgraded.

I'm sure it must be something simple.

I did remove 5.0.2 from my applications folder before I dragged 5.0.3 into it - perhaps that has done something?

Its a bit annoying & any help will be greatly appreciated.

[shypike]

Try 127.0.0.1:8080/sabnzbd or [::1]:8080/sabnzbd instead.

[Bubby]

I had a bit of a read earlier & tried those shypike. I tried them again - just to make sure, but I get the same page


Is there anything else I could try? Thank you for the help.

[sander]

@Bubby,

So you're sure SABnzbd is running? If so: Has MacOXS got "nmap"? If so, run "nmap localhost" to see which ports are listening; maybe SABnzbd is listening on another port than 8080

Here's my own output:

Code: Select all

sander@quirinius:~$ nmap localhost

Starting Nmap 5.00 ( http://nmap.org ) at 2010-08-13 19:04 CEST
Warning: Hostname localhost resolves to 2 IPs. Using 127.0.0.1.
Interesting ports on localhost (127.0.0.1):
Not shown: 991 closed ports
PORT      STATE SERVICE
21/tcp    open  ftp
53/tcp    open  domain
80/tcp    open  http
119/tcp   open  nntp
139/tcp   open  netbios-ssn
445/tcp   open  microsoft-ds
631/tcp   open  ipp
8080/tcp  open  http-proxy
10000/tcp open  snet-sensor-mgmt

Nmap done: 1 IP address (1 host up) scanned in 0.56 seconds
sander@quirinius:~$ 

[Bubby]

Hi Sander - thank you very very much for the help.

I have a Network Utility on my Mac, so I ran Netstat & selected "display the state of all current socket connections". I looked for the closest thing to 8080 & I seen "tcp6       0      0  localhost.8085         *.*                    LISTEN".


So, I selected http://localhost:8085/sabnzbd/ & hey presto - it worked!

Now just one question....


Why would it have changed fro 8080 to 8085?

Thank you so much! Im happy now

[sander]

@"Why would it have changed fro 8080 to 8085?"

... because you are (or were) apparantly already running something else on port 8080 (check with netstat or nmap), which is discovered by SABnzbd, which therefore will hunt (in steps of 5) for a free port above 8080 ...


EDIT: maybe it can also happen if SAB instance #1 is already running on 8080, and you start (by accident) another instance #2 of SAB, which will then be on port 8085, which will get written into sabnzbd.ini, and then reused next time ...

[Bubby]

That's great Sander, I really appreciate your help. Top man - thanks!