can't get sabnzbd working on my mac

[wilsonfisk]

downloaded the sabnzbd program from this site, copied it to my applications folder. when i start it up, it opens a new tab in firefox at the address: http://localhost:8080/sabnzbd and it just displays a "failed to connect" message. it creates the complete and incomplete folders in my downloads folder though.

anyone else have this problem?

[shypike]

Try http://127.0.0.1:8080/sabnzbd or else http://[::1]:8080/sabnzbd

[wilsonfisk]

http://[::1]:8080/sabnzbd

this worked. thanks!!!

why is it that this was the address i had to use to pull it up?

[switch]

What version of firefox are you using? 2?

On some operating systems localhost can mean 127.0.0.1 (an ipv4 address) and on others it can mean [::1] (an ipv6 address). It looks like your browser is not respecting the operating system's choice.

[wilsonfisk]

im using the most current verison of firefox i believe its version 3.x.x

when i first installed it, i also tried using safari and it didnt work there as well.

can i configure the sabnzbd program so that it doesnt go to localhost:8080 everytime it starts?

[switch]

If you go into config>general and delete the value for "Host" (leaving it blank) then restart sabnzbd it will listen on your local ip address instead.

[shypike]

Or put [::1] or 127.0.0.1 in the Host field.

Maybe we should not default to localhost for OSX.

[wilsonfisk]

whats strange is, i installed sabnzbd on my macbook pro which is running the same version of os x (10.5.5 or 6) and it started up perfectly the first time. when i went home and did it on my iMac, i ran into the localhost problem. the only difference between the 2 computers is, they both connect via wifi, one connects to a verizon wireless actiontec router and my imac connects via wifi to an airport base station. both also using the same version of firefox.

[sander]

whats strange is, i installed sabnzbd on my macbook pro which is running the same version of os x (10.5.5 or 6) and it started up perfectly the first time. when i went home and did it on my iMac, i ran into the localhost problem. the only difference between the 2 computers is, they both connect via wifi, one connects to a verizon wireless actiontec router and my imac connects via wifi to an airport base station. both also using the same version of firefox.

On each/both machine, what happens if you open a terminal screen / command box (I don't know the name on Mac), and you "ping localhost"?
Does the file /etc/hosts exist, and does it contain a line "127.0.0.1      localhost"?

[wilsonfisk]

On each/both machine, what happens if you open a terminal screen / command box (I don't know the name on Mac), and you "ping localhost"?
Does the file /etc/hosts exist, and does it contain a line "127.0.0.1       localhost"?

i get the same message when pinging localhost on both machines. looks like this "64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.032 ms" and it pings a bunch of more times, thats just the first line. not sure where the hosts file would be on my mac.

[sander]

On each/both machine, what happens if you open a terminal screen / command box (I don't know the name on Mac), and you "ping localhost"?
Does the file /etc/hosts exist, and does it contain a line "127.0.0.1       localhost"?

i get the same message when pinging localhost on both machines. looks like this "64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.032 ms" and it pings a bunch of more times, thats just the first line. not sure where the hosts file would be on my mac.

So 'localhost' is correctly resolved. That's good.

And, just checking:

http://localhost:8080/sabnzbd does not work?
http://127.0.0.1:8080/sabnzbd does or does not work?
http://[::1]:8080/sabnzbd does work?

On the 'non-working' Mac, is there a firewall active?

[wilsonfisk]

On each/both machine, what happens if you open a terminal screen / command box (I don't know the name on Mac), and you "ping localhost"?
Does the file /etc/hosts exist, and does it contain a line "127.0.0.1       localhost"?

i get the same message when pinging localhost on both machines. looks like this "64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.032 ms" and it pings a bunch of more times, thats just the first line. not sure where the hosts file would be on my mac.

So 'localhost' is correctly resolved. That's good.

And, just checking:

http://localhost:8080/sabnzbd does not work?
http://127.0.0.1:8080/sabnzbd does or does not work?
http://[::1]:8080/sabnzbd does work?

On the 'non-working' Mac, is there a firewall active?

http://localhost:8080/sabnzbd - DOESNT WORK
http://127.0.0.1:8080/sabnzbd  - DOESNT WORK
http://[::1]:8080/sabnzbd - WORKS

[sander]

http://localhost:8080/sabnzbd - DOESNT WORK
http://127.0.0.1:8080/sabnzbd  - DOESNT WORK
http://[::1]:8080/sabnzbd - WORKS

So it seems the IPv4 connection is blocked, and IPv6 is not blocked.

Is there a firewall active on the Mac? If so, is might be blocking IPv4 traffic to the Mac
What is filled out "Host" in config -> general?

[switch]

If localhost resolves to an ipv4 address then sabnzbd should really be listening on that. I can't remember what checks we do offhand, but I thought we checked if localhost is ambiguous.

I wonder why it works on some OSX systems but not others.

[sander]

If localhost resolves to an ipv4 address then sabnzbd should really be listening on that.

... but in between could be a IPv4-only firewall ...
Not probable, but we should check it.

I can't remember what checks we do offhand, but I thought we checked if localhost is ambiguous.

I wonder why it works on some OSX systems but not others.

Ah, it happens more often?