Fame Burst

Home / updates

Google Chrome can't access localhost domains

Mia Cox |

This is my first time trying Chrome and I can't access localhost, 127.0.0.1 or any other local domain I have setup from within Chrome 29.0.1547.66. They all work fine in Firefox and Internet Explorer, and have for years.

Nothing happens at all in Chrome when I try to load one of these pages. Loading icon just spins indefinitely.

What's up with Chrome?

System: Windows 8
Server: Softaculous AMPPS 2.0

Additional troubleshooting performed with @50-3 in comments; comments have since been removed to free up space

  • Disabled same origin policy --disable-web-security
  • Tried accessing via 127.0.0.1:80,
  • Server not yet configured to allow connection from network IP address
3

5 Answers

I finally found a solution to this. Go to chrome://flags and set "Built-in Asynchronous DNS" to "Disabled", then restart the browser.

This allows all local domains to be accessed. Looks like DNS was just choking up the issue.

6

Plagiarizing from Louie Bertoncin's answer on Chrome: how to stop redirect from http:// to https://--

My problem came from having a .dev domain, which was apparently recently registered as a [generic top-level-domain] and put in a commit to Chrome Canary. I found this out from a recent post I came across as I searched for my problem.

If you have the same problem I do, it appears that the best solution is to change your domain to be something other than .dev. The article suggested .test with a potential solution of .localhost later down the road (via this proposal).

2

The solution is this one. Go to chrome Settings -> Advances settings -> Privacy

And uncheck all options except this: "Protect you and your device from dangerous sites"

Will work !

3

@sparrow had the right answer for me, but it was buried in the comments. I am hoping this helps someone else. @EcomEvo mentioned going to chrome://flags and looking for the "Built-in Asynchronous DNS". Since his answer is old, that is no longer an option in Chrome. However, I just did what @sparrow did. Under "chrome://flags", I just chose "Reset all settings to default" and it started working again.

1

This worked for me: suffix the port number

Problem with this URL:

Just add the Port number:

Problem solved:

Port number will vary based on what you use, XAMPP, APACHE, NGINX, Homestead.

I use Homestead.

3

You Might Also Like