Are you using a proxy?

No

Also. I thought that this is problems of the extensions, that's why I've renamed 
~/.config/chromium to ~/.config/chromium_ and run Cromium with an empty profile. The 
situation is the same.

Hmmm ... http://localhost works happily for me (r36495, 32 bit)

What error do you get "Page not found - connection failure" ??

chrome://net-internals/ and searching for localhost in there after trying to load the 
page may yield some more useful information.

You can enable/disable extensions through chrome://extensions/ btw. and there is a 
command line option too ... probably --disable-extensions IIRC - that might be easier 
than messing with the config dir.

>What error do you get "Page not found - connection failure" ??
Yes. I took this error:
============
Page not found - connection failure

Oops! This link appears to be broken.
Suggestion:
Search on Google:
============

>chrome://net-internals/ and searching for localhost in there after trying to load 
the page may yield some more useful information.
I can see only this:
========
http://localhost/
t=85906563: +URL_REQUEST_START                                     [dt=0]
t=85906563:    HTTP_CACHE_OPEN_ENTRY                               [dt=0]
t=85906563:    HTTP_CACHE_CREATE_ENTRY                             [dt=0]
t=85906563:    HTTP_CACHE_WAITING                                  [dt=0]
t=85906563:    PROXY_SERVICE                                       [dt=0]
t=85906563:   +SOCKET_POOL                                         [dt=0]
t=85906563:     +SOCKET_POOL_CONNECT_JOB                           [dt=0]
t=85906563:       +HOST_RESOLVER_IMPL                              [dt=0]
t=85906563:          HOST_RESOLVER_IMPL_OBSERVER_ONSTART           [dt=0]
t=85906564:          HOST_RESOLVER_IMPL_OBSERVER_ONFINISH          [dt=0]
t=85906564:       -HOST_RESOLVER_IMPL
t=85906564:        TCP_CONNECT                                     [dt=0]
t=85906564:        TCP_CONNECT                                     [dt=0]
t=85906564:     -SOCKET_POOL_CONNECT_JOB
t=85906564:   -SOCKET_POOL
t=85906564:    PROXY_SERVICE_POLL_CONFIG_SERVICE_FOR_CHANGES       [dt=0]
t=85906564: -URL_REQUEST_START
=========

I found the problem: this is because only when the servers listen tcp6 only.

IE
netstat -nat|grep ":80 "
========
tcp6       0      0 ::1:80                  :::*                    LISTEN
========

And Chrome can't connect to tcp6 port. but all other browsers can. If I changed the 
servers to use tcp4 port too, then all is OK with Chromium.

Does http://localhost6 work for you btw.? That should in theory resolve to ::1

No. It redirects me to http://www.localhost6.com/

Hmmm ... on my fedora machine I have localhost6 == ::1 in hosts and Ulrich (the main 
glibc guy) seems to think that is correct and that localhost should not be aliased to 
::1 ... see link below. That doesn't yet explain why firefox works though.

There is some python you can run in the link below too btw., the output of which may 
be interesting.

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=496300

So your web server is listening on [::1]:80, but http://localhost/ does not work?

How are you expecting this to work? Does /etc/hosts set localhost to ::1 ? On my 
ubuntu at least, ::1 is ip6-localhost, not localhost. Does http://ip6-localhost work?

in my /etc/hosts file there is
127.0.0.1 localhost
::1       localhost ip6-localhost ip6-loopback

And all other browsers can connect to [::1]:80, but not Chromium

to l.colitti
>Does http://ip6-localhost work?

No. Also http://ip6-loopback/ does not work for Chromium. But Firefox can connect to 
http://ip6-localhost http://ip6-loopback/ and to http://localhost/

(No comment was entered for this change.)

alex.fomenko: could you compile and run the two test programs in
http://code.google.com/p/chromium/issues/detail?id=12711#c15
on your computer?  Please pass 'localhost' as the input to
the test programs.

Here is an output

alex@mirage:~/sources/test>./getaddr1 localhost
127.0.0.1
127.0.0.1
alex@mirage:~/sources/test>./getaddr2 localhost
::1
127.0.0.1

BTW I have Ubuntu 9.10(x86_64) with KDE at my laptop. And the same version of the 
Chromium. There all is OK (Chromium can connect to the tcp6 port). But output of 
these commands are the same.

alex.fomenko:  Thanks a lot.  Could you also post the output of the
"ifconfig -a" command on your laptop?

The only difference between these two test programs is that getaddr1.cc
uses the AI_ADDRCONFIG flag but getaddr2.cc doesn't.

Firefox does not use the AI_ADDRCONFIG flag on Linux, so Firefox
behaves like getaddr2 and gets the ::1 address for "localhost".
Linux Chrome behaves like getaddr1.

It seems that AI_ADDRCONFIG does not interact well with the addresses
of the loopback network interface.  I suspect that AI_ADDRCONFIG uses
the capabilities of the *outgoing* (non-loopback) network interfaces
to determine what kinds of address (IPv4 or IPv6) to return, but it
applies the same filtering to loopback addresses.  If the loopback
interface can do IPv6 but the non-loopback interface can't, the ::1
address will be filtered out incorrectly.  Again, this is just my
speculation.

alex@miracle:~>ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:1f:c6:24:89:ae
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:31 Base address:0x2000

lo        Link encap:Локальная петля (Loopback)
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5751 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5751 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6445252 (6.4 MB)  TX bytes:6445252 (6.4 MB)

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:1f:3c:02:62:19
          inet addr:192.168.123.4  Bcast:192.168.123.255  Mask:255.255.255.0
          inet6 addr: fe80::21f:3cff:fe02:6219/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:677066 errors:0 dropped:0 overruns:0 frame:0
          TX packets:396348 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:762004611 (762.0 MB)  TX bytes:108816849 (108.8 MB)

wmaster0  Link encap:UNSPEC  HWaddr 00-1F-3C-02-62-19-00-00-00-00-00-00-00-00-00-00
          UP RUNNING  MTU:0  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

I get the same issue, only while offline. I. e. I disconnect and http://localhost:8888 
(my own development server) stops working in Chromium, but it works in firefox. It 
does not matter if I call it as http://127.0.0.1:8888/ (or http://[::1]:8888/ but 
ipv6 addresses not working while AAAA named hosts doing it is a different bug)

5.0.364.0 (42891) Ubuntu here

santiago.gala: thanks for the info.  Could you post the output of the
"ifconfig -a" command *when your computer is offline*?

Same problem here using Mac: 
 'The server denies connections.'

If I go offline I get: 
'This webpage is not available. Error 102 (net::ERR_CONNECTION_REFUSED): Unknown error.'


Mac, Google Chrome 5.0.360.4 (Official Build 42897) dev

People who experience this bug, please do the following, while
your computer is offline:

1. Follow the instructions in comment 15 and provide the output
of those two test programs.

2. Provide the output of the "ifconfig -a" command.

Sorry I'm no programmer so I'm not sure if I did the right thing:
downloaded the 2 scripts and copy pasted the provided lines in the terminal (was that right?) 
If what I did was wrong, please explain step by step procedure - tnx

========================

g++ -Wall getaddr1.cc -o getaddr1
./getaddr1 www.virus.org
213.239.218.185

 g++ -Wall getaddr2.cc -o getaddr2
./getaddr2 www.virus.org
213.239.218.185

========================

ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::21f:5bff:fe3c:2ba8%en0 prefixlen 64 scopeid 0x4 
	inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
	ether 00:1f:5b:3c:2b:a8 
	media: autoselect (100baseTX <full-duplex>) status: active
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 
1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 00:1f:5b:3c:2b:a9 
	media: autoselect status: inactive
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 
1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
	lladdr 00:22:41:ff:fe:51:69:a6 
	media: autoselect <full-duplex> status: inactive
	supported media: autoselect <full-duplex>
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 00:1f:5b:e1:f7:98 
	media: autoselect status: inactive
	supported media: none autoselect 10baseT/UTP <half-duplex>

========================

When I try http://localhost in the Consol I get

2/4/10 2 April  8:26:52 [0x0-0x178178].com.google.Chrome[1780] [0402/202652:WARNING:/b/slave/chrome-official-mac/build/src/chrome/app/breakpad_mac.mm(62)] Breakpad disabled 

2/4/10 2 April  8:26:52 com.apple.launchd[151] (0x10dbc0.Google Chrome He[2024]) Policy denied Mach service lookup: com.apple.windowserver.session 

2/4/10 2 April  8:26:52 [0x0-0x178178].com.google.Chrome[1780] Fri Apr  2 20:26:52 MyComputer.local Google Chrome Helper[2024] <Error>: The function `CGAccessSessionSkipBytes' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete 
function, and is thereby contributing to an overall degradation of system performance. Please use `CGAccessSessionSkipForward' instead. 

========================

Sorry forgot the files
Mac, Google Chrome 5.0.360.4 (Official Build 42897) dev

getaddr1 12.5 KB   Download

getaddr2 12.5 KB   Download

Sorry forgot the files
Mac, Google Chrome 5.0.360.4 (Official Build 42897) dev

ycc2106: Re: comment 23: here are the step-by-step instructions.

1. Shut down Chrome.

2. Go offline.  Your Mac should not be connected to any network.

3. Start Chrome and visit http://localhost/  Do you get an error page?
What does the error page say?

4. Stay offline.  Open a Terminal window.  Run these three commands in
Terminal:
  ./getaddr1 localhost
  ./getaddr2 localhost
  ifconfig -a

(No comment was entered for this change.)

I spotted an interesting comment here:
http://crbug.com/39830#c1
that may explain some "ipv6 localhost doesn't work" situations btw.

Executive summary: try "--enable-ipv6"

In case, tried:
exec /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-ipv6
went to http://localhost and got:

The server denies connections.
The server might be too busy or might be disabled. Try again a bit later.


@wtc
1. Shut down Chrome.
2. Go offline.  Your Mac should not be connected to any network. <- turned everything OFF
3. Start Chrome and visit http://localhost/  Do you get an error page?
What does the error page say?

This webpage is not available.
The webpage at http://localhost/ might be temporarily down or it may have moved permanently to a new web 
address.

4. Stay offline.  Open a Terminal window.  Run these three commands in Terminal (...! stupid ;P):

  ./getaddr1 localhost
::1
fe80::1
127.0.0.1

  ./getaddr2 localhost
::1
fe80::1
127.0.0.1


      ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::21f:5bff:fe3c:2ba8%en0 prefixlen 64 scopeid 0x4 
	ether 00:1f:5b:3c:2b:a8 
	media: autoselect (100baseTX <full-duplex>) status: active
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP 
<full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX 
<full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT 
<full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 00:1f:5b:3c:2b:a9 
	media: autoselect status: inactive
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP 
<full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX 
<full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT 
<full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
	lladdr 00:22:41:ff:fe:51:69:a6 
	media: autoselect <full-duplex> status: inactive
	supported media: autoselect <full-duplex>
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 00:1f:5b:e1:f7:98 
	media: autoselect status: inactive
	supported media: none autoselect 10baseT/UTP <half-duplex>


Did I get it right this time? o_0

(No comment was entered for this change.)

I have almost the same problem when my wireless connection goes down
with 5.0.375.29 beta / ubuntu 9.10

 The webpage at http://localhost/ might be temporarily down or it may have moved 
permanently to a new web address.

Erreur 105 (net::ERR_NAME_NOT_RESOLVED) : Serveur Introuvable

When the connection is up again i can connect again on http://localhost

I'm running google chrome v. 5.0.375.29 (Official Build 46008) beta on Kubuntu v. 10.04.

Not only am I having the problem with localhost, but the resolver seems to fail on
the ip address too. Should it be trying to resolve ip addresses?

jon@nano:~/chrome-test$ ./getaddr1 localhost
127.0.0.1
127.0.0.1
jon@nano:~/chrome-test$ ./getaddr2 localhost
::1
127.0.0.1

jon@nano:~/chrome-test$ ./getaddr1 127.0.0.1
127.0.0.1
jon@nano:~/chrome-test$ ./getaddr2 127.0.0.1
127.0.0.1

jon@nano:~/chrome-test$ netstat -tl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 localhost:ipp           *:*                     LISTEN     
tcp        0      0 localhost:8000          *:*                     LISTEN     
tcp6       0      0 localhost:ipp           [::]:*                  LISTEN     

eth0    Link encap:Ethernet  HWaddr 00:18:8b:a8:14:13  
		UP BROADCAST MULTICAST  MTU:1500  Metric:1
		RX packets:0 errors:0 dropped:0 overruns:0 frame:0
		TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:1000 
		RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
		Interrupt:18 

lo      Link encap:Local Loopback  
		inet addr:127.0.0.1  Mask:255.0.0.0
		inet6 addr: ::1/128 Scope:Host
		UP LOOPBACK RUNNING  MTU:16436  Metric:1
		RX packets:34890 errors:0 dropped:0 overruns:0 frame:0
		TX packets:34890 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:0 
		RX bytes:27075930 (27.0 MB)  TX bytes:27075930 (27.0 MB)

pan0    Link encap:Ethernet  HWaddr ee:c2:44:7c:37:71  
		BROADCAST MULTICAST  MTU:1500  Metric:1
		RX packets:0 errors:0 dropped:0 overruns:0 frame:0
		TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:0 
		RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0   Link encap:Ethernet  HWaddr 00:18:de:9b:b2:8c  
		BROADCAST MULTICAST  MTU:1500  Metric:1
		RX packets:15502166 errors:0 dropped:0 overruns:0 frame:0
		TX packets:15625736 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:1000 
		RX bytes:1538536900 (1.5 GB)  TX bytes:3202637717 (3.2 GB)

Google chrome with 'localhost'

This webpage is not available.

The webpage at http://localhost:8000/ might be temporarily down or it may have moved
permanently to a new web address.

Here are some suggestions:
Reload this web page later.
  More information on this error
  Below is the original error message

  Error 105 (net::ERR_NAME_NOT_RESOLVED): The server could not be found.

Google Chrome with '127.0.0.1'

This webpage is not available.

The webpage at http://127.0.0.1:8000/ might be temporarily down or it may have moved
permanently to a new web address.

Here are some suggestions:
Reload this web page later.
  More information on this error
  Below is the original error message

  Error 105 (net::ERR_NAME_NOT_RESOLVED): The server could not be found.

Just out of curiosity, are the routines in chrome checking the /etc/hosts file after
the nameservers fail as unreachable?  

From what I can see, the AI_CANONNAME flag is not set for getaddrinfo().  On my
system, this seems to prevent resolution of localhost when there are no namesevers
available.  Take a look at this:

jon@nano:~/chrome-test$ ./getaddrinfo localhost
--- looking up 'localhost' for family 0 (0)
getaddrinfo(...) = EAI_NONAME, trying again with AI_CANONNAME
getaddrinfo(...) = 0
getnameinfo(...) = 0
        name = ::1
        service = 23
getnameinfo(...) = 0
        name = 127.0.0.1
        service = 23
--- looking up 'localhost' for family AF_INET (2)
getaddrinfo(...) = EAI_NONAME, trying again with AI_CANONNAME
getaddrinfo(...) = 0
getnameinfo(...) = 0
        name = 127.0.0.1
        service = 23
getnameinfo(...) = 0
        name = 127.0.0.1
        service = 23
--- looking up 'localhost' for family AF_INET6 (10)
getaddrinfo(...) = EAI_NONAME, trying again with AI_CANONNAME
getaddrinfo(...) = 0
getnameinfo(...) = 0
        name = ::1
        service = 23

I found the previous program on a Gentoo bug here: http://bugs.gentoo.org/199025

It also has some further info.

same issue here as #32

Ubuntu 9.04 / GNOME 2.26.1

While offline:

$ ./getaddr1 localhost
127.0.0.1
127.0.0.1
$ ./getaddr2 localhost
::1
127.0.0.1
$ ./getaddr1 127.0.0.1
127.0.0.1
$ ./getaddr2 127.0.0.1
127.0.0.1



$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:145827 errors:0 dropped:0 overruns:0 frame:0
          TX packets:197780 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:50237877 (50.2 MB)  TX bytes:199121696 (199.1 MB)
          Memory:f2600000-f2620000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:130522 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130522 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:17657865 (17.6 MB)  TX bytes:17657865 (17.6 MB)

pan0      Link encap:Ethernet  HWaddr 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vboxnet0  Link encap:Ethernet  HWaddr 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan1     Link encap:Ethernet  HWaddr 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 Memory:f8098000-f8098100 

Is port 80 protected (running webserver as root?).

This has nothing to do with anything other then name resolution, for me.  Other
browsers (Firefox and Konqueror) work fine both online and offline.  If you look at
the link to the Gentoo bug report in #35, there is mention that Mozilla had to code
around this issue for Firefox.

(No comment was entered for this change.)

Here's the Mozilla bug report. https://bugzilla.mozilla.org/show_bug.cgi?id=467497

I just updated to 5.0.375.70-r48679 google-chrome-beta for Ubuntu Lucid.  This is
still a bug.  Here is the error:

Error 105 (net::ERR_NAME_NOT_RESOLVED): The server could not be found.

Hy!

What is strange that I can connect to my localhost server until I have an active 
network connection, but without that, I get Error 105 (net::ERR_NAME_NOT_RESOLVED): 
The server could not be found.

Ubuntu Lucid 64bit
Google Chrome 6.0.422.0 dev

(No comment was entered for this change.)

 Issue 34299  has been merged into this issue.

(No comment was entered for this change.)

This may be a dup of  bug 39830 .
See https://spreadsheets0.google.com/ccc?key=tVHFlSRv-d8c_yJrPj0z8aA&authkey=CLKDxMYB&hl=en#gid=0

is there any solution for this? 

I have code to fix this but I haven't committed it in yet.  There are a number of interrelated bugs and I want to make sure they all get fixed.  This spread sheet shows the state of things before I started looking at this on top and my local state at the bottom. https://spreadsheets.google.com/ccc?key=0AhSnKEusL6UgdFZIRmxTUnYtZDhjX3lKclBqMHo4YUE&hl=en&authkey=CLKDxMYB

This will certainly be fixed by M7 and this issue will be updated when I check in the fix, so you'll get a notification.

I have had issues with this too. I run a server on http://127.0.0.1:8000 and no matter whether I use the IP address 127.0.0.1:8000 or localhost:8000 this error pops up and at the same time Firefox works fine and loads these URLs okay

Btw, I use Google Chrome stable on Ubuntu Lucid Lynx 32-bit

I'm seeing the same issue.  I'm running Ubuntu Linux.  I've got a server running on localhost, and it works with Firefox, but I get an "Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error." when I try and connect with Chrome.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=58534 

------------------------------------------------------------------------
r58534 | vandebo@chromium.org | 2010-09-03 13:34:27 -0700 (Fri, 03 Sep 2010) | 10 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/net/base/address_family.h?r1=58534&r2=58533
   M http://src.chromium.org/viewvc/chrome/trunk/src/net/base/host_resolver_impl.cc?r1=58534&r2=58533
   M http://src.chromium.org/viewvc/chrome/trunk/src/net/base/host_resolver_proc.cc?r1=58534&r2=58533
   M http://src.chromium.org/viewvc/chrome/trunk/src/net/base/mock_host_resolver.cc?r1=58534&r2=58533

Fix remaining localhost resolution issues.

If host resolution is restricted to a single address family and the results of a resolution are all localhost of that type, try again without the address family restriction.

Also make --disable-ipv6 apply to resolution of ip literals.

BUG=42058, 49024, 32522
TEST=Manual testing in various network configurations. See https://spreadsheets.google.com/ccc?key=0AhSnKEusL6UgdFZIRmxTUnYtZDhjX3lKclBqMHo4YUE&hl=en&authkey=CLKDxMYB

Review URL: http://codereview.chromium.org/3231005
------------------------------------------------------------------------

I made several changes to address this and all related bugs.  If you continue to experience problems related to this bug after r58535, please create a new bug and reference it here.  There is much conflicting information in this bug report, so a fresh start for any further issues would be helpful.

Verified label updated by AutoAllocator, contact AmolK or KrisR for details

Still having the same problem for 6.0.472.63~r59945-0ubuntu2 from the ubuntu maverick/universe repo. 

 Oops! Google Chrome could not connect to localhost

Http server is thttpd, and there is no way to configure it to listen on tcp 4. 

$ ps -eaf | grep [t]httpd
www-data  9613     1  0 10:54 ?        00:00:00 /usr/sbin/thttpd -C /etc/thttpd/


$ netstat -nat|grep ":80 "
tcp6       0      0 :::80                   :::*                    LISTEN     

Please open a new bug and then note the number here.  Providing the following debug information (when you can reproduce the bug) will also help:

Output of the following commands:
host localhost
dig -tany +noall _answer localhost
ifconfig
google-chrome --version

Contents of the following files:
/etc/hosts
/etc/resolv.conf
/etc/host.conf
/etc/nsswitch.conf

Contents of the webpage
chrome://net-internals/#dns