Page 1 of 1
0.0.0.0 not accessible in opera browser
Posted: November 8th, 2009, 5:26 pm
by aaa444
0.0.0.0 pages are not accessible through opera for some reason
sabnzbd+ 0.5.0 alpha 9 on os x has menu bar items that opens pages to ip 0.0.0.0 (e.g.
http://0.0.0.0:8080/sabnzbd/connections/) in my default browser, opera. sabnzbd host is set to 0.0.0.0, but is there a way to set it to something else for the menu bar, like localhost or
hostname.local
Re: 0.0.0.0 not accessible in opera browser
Posted: November 8th, 2009, 5:48 pm
by shypike
You cannot use 0.0.0.0 in any web browser.
It just means that SABnzbd will listen to all available interfaces.
Usually this is "localhost" and the IP address of your system.
If the browser and SABnzbd are on the same system, use:
http://localhost:8080/sabnzbd
Re: 0.0.0.0 not accessible in opera browser
Posted: November 8th, 2009, 6:44 pm
by inpheaux
Opera won't listen on localhost either. This isn't our fault, they just plain won't do it.
You'll probably need to use the ipv6 address http://[::1]:8080/sabnzbd
Re: 0.0.0.0 not accessible in opera browser
Posted: November 9th, 2009, 7:34 am
by aaa444
shypike wrote:
You cannot use 0.0.0.0 in any web browser.
It just means that SABnzbd will listen to all available interfaces.
Usually this is "localhost" and the IP address of your system.
If the browser and SABnzbd are on the same system, use:
http://localhost:8080/sabnzbd
do you mean 0.0.0.0 shouldn't be used? it works fine in safari/firefox. if you did mean it shouldn't be used, maybe the link the menubar item opens should be changed to something else?
inpheaux wrote:
Opera won't listen on localhost either. This isn't our fault, they just plain won't do it.
You'll probably need to use the ipv6 address http://[::1]:8080/sabnzbd
I think this used to be true, but it works fine now.
Re: 0.0.0.0 not accessible in opera browser
Posted: November 9th, 2009, 9:53 am
by sander
Funny:
http://0.0.0.0:8080/sabnzbd/ works with my Firefox on Ubuntu. And
http://0.0.0.0:8080/ works too. And even ping to 0.0.0.0 works:
sander@quirinius:~$ ping 0.0.0.0
PING 0.0.0.0 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.116 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.071 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.069 ms
^C
--- 0.0.0.0 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.069/0.085/0.116/0.022 ms
sander@quirinius:~$
I thought 0.0.0.0 meant default route. Maybe it's the difference between 0.0.0.0/0 (default route) and 0.0.0.0/32 ?