Page 1 of 1
new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 2:29 am
by songkran
I recently upgraded Google Chrome to the newest version in OS X and it can't access
http://localhost:8080/ although Safari and other browsers can.
Is there something I need to do to help Chrome "see"
http://localhost:8080/ ?
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 2:44 am
by shypike
Firefox once had a problem with localhost too, it had to do with IPV4 vs. IPV6.
Try 127.0.0.1:8080 or [::1]:8080 instead.
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 3:06 am
by songkran
Thanks, Shypike. Changing it to the static IP pf the machine running sabnzbd in settings (192.168.0.XXX) ended up working for me.
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 4:18 am
by djapplepie
Similar problem here. Just updated Google Chrome to 5.0.375.29. I am running SABnzbd+ 0.5.2 on Mac OS X 10.6.3.
Here are the results from the browsers I tried:
Google Chrome 5.0.375.29 beta
- localhost:8080 — NOT working
- 127.0.0.1:8080 — NOT working
- [::1]:8080 — NOT working
Firefox 3.6.3
- localhost:8080 — working
- 127.0.0.1:8080 — NOT working
- [::1]:8080 — working
Safari 4.0.5
- localhost:8080 — working
- 127.0.0.1:8080 — NOT working
- [::1]:8080 — working
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 7:27 am
by shypike
Time to complain to Google.
From your results it's plain that localhost resolves to the IPV6 address [::1].
I have no idea why Chrome has problems with this, unless it thinks it knows better
than the OS what localhost is.
Safari and Firefox agree that it's [::1].
What happens if you type "ping localhost" in a terminal window?
An alternative is to tell SABnzbd to use 127.0.0.1 instead of localhost.
Config->General.
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 9:23 am
by songkran
djapplepie-- I was mistaken. The last thing I tried was changing it to the static IP of the machine running sabnzbd (192.168.0.XXX) in settings. I mistakenly thought if this worked that 127.0.0.1 worked too. Didn't know Chrome was so sensitive.
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 11:57 am
by inpheaux
Looks like this is either a Mac or Unix bug, because localhost works perfectly fine for me with the latest Chrome beta on Win7, and SABnzbd listening on "localhost".
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 3:20 pm
by djapplepie
shypike wrote:
What happens if you type "ping localhost" in a terminal window?
I get this:
Code: Select all
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.045 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.071 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.072 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.072 ms
...
Looks ok, right?
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 5th, 2010, 3:53 pm
by djapplepie
shypike wrote:
An alternative is to tell SABnzbd to use 127.0.0.1 instead of localhost.
Config->General.
I told SABnzbd to use 127.0.0.1 instead of localhost, and
Chrome works again (both localhost:8080 and 127.0.0.1:8080). The other two browsers also works. However, [::1]:8080 doesn't.
Chrome was the only browser out of the three I tested that behaved differently when the SABnzbd Host setting was localhost.
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: May 7th, 2010, 1:57 am
by allanpro
You are life saviors!! Thanks a bunch!
Re: new version of Google Chrome can't access http://localhost:8080/
Posted: July 17th, 2010, 7:13 pm
by opt
I signed up just to say yayyyy this works! thank you!111