Chrome: issues with using localhost after an upgrade

Hello,

After I upgraded Chrome to its newest version suddenly I was no longer able to view the sites I develop using my localhost (127.0.0.1) address.
It displays nothing - well, it displays an error message that the site couldn’t be found.

Firefox and other browsers work as they normally would, the only issue I have is with Chrome.

Could anyone shed some light onto this subject?
Thank you very much!

Cheers,
Greg

Since it is a local web host, can you look into the logs? It may give you a clue of what’s going on

1 Like

I usually go to http://localhost not http://127.0.0.1 but it’s still working for me.
Maybe it’s a config issue?
My first guess would be that the server isn’t running, but if other browsers are working it shouldn’t be that.

Try explicitly placing http in front ie. http://localhost

Hey,

thank you all for your inputs!
The stuff I posted was completely off, the person who asked me to post this issue had something else in mind.

“My Chrome’s version is 43.0.2357.81 m.Chrome doesn’t read ip from /etc/hosts for subdomains localhost (another 127.0.0.1). Localhost in Windows is reserved, but sudomain of localhost is allowed another ip set in etc/hosts.
I have Windows 8.”

We are using machines with Virtual Server installed, and usually we operate on subdomains of localhost, eg. en.localhost/my_project/

While every such address is accessible via Firefox, Opera, Safari etc, Chrome fails to access it.
Is it a bug or was this way of viewing local projects removed from Chrome?
Is there a way to fix it somehow?

Thank you!

Cheers,
Greg

It is still hard to tell if Chrome is at fault or not. Maybe Chrome does reach the server although it looks more like it doesn’t. I still wonder if there’s any record in the logs

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.