Google Chrome can't access localhost domains Announcing the arrival of Valued Associate #679:...
ListPlot join points by nearest neighbor rather than order
I am not a queen, who am I?
Right-skewed distribution with mean equals to mode?
Why is "Captain Marvel" translated as male in Portugal?
Using et al. for a last / senior author rather than for a first author
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
What are the pros and cons of Aerospike nosecones?
What is a Meta algorithm?
What's the purpose of writing one's academic bio in 3rd person?
If Jon Snow became King of the Seven Kingdoms what would his regnal number be?
List *all* the tuples!
Why is "Consequences inflicted." not a sentence?
What is the longest distance a 13th-level monk can jump while attacking on the same turn?
Why are there no cargo aircraft with "flying wing" design?
How to deal with a team lead who never gives me credit?
Is there a documented rationale why the House Ways and Means chairman can demand tax info?
Antler Helmet: Can it work?
Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?
Letter Boxed validator
Why does Python start at index -1 when indexing a list from the end?
Why aren't air breathing engines used as small first stages
Do you forfeit tax refunds/credits if you aren't required to and don't file by April 15?
Do I really need recursive chmod to restrict access to a folder?
When is phishing education going too far?
Google Chrome can't access localhost domains
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How to stop an automatic redirect from “http://” to “https://” in ChromeChrome Localhost Connection RefusedHow to avoid google chrome proxy bypass for localhost?Google Chrome is slow to localhostGoogle Chrome on Mac and localhost issuesGoogle(.com) stops loading sometimesHow do I disable XSS/“Same Origin” checking on Chrome?Google Chrome can't access website and redirects behave strangelyCan I disable Google Chrome Autofill ONLY for localhost?Stop Google Chrome from using Google ipv6 DNS?Firefox & Chrome download PHP Files. While other browsers work… :sChrome gives SSL warning on Google domains“Aw, snap!” messages on any action in Google Chrome on macOS
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
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,http://localhost:80
- Server not yet configured to allow connection from network IP address
google-chrome
edited Sep 17 '13 at 1:49
50-3
3,67931527
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
add a comment |
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,http://localhost:80
- Server not yet configured to allow connection from network IP address
google-chrome
edited Sep 17 '13 at 1:49
50-3
3,67931527
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
The answer on this SO Q&A stackoverflow.com/questions/30467573/… is what worked for me. You need to clear out Chrome's DNS cache through this internal Chrome URL - chrome://net-internals/#dns.
– slm
Apr 19 '18 at 1:50
add a comment |
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,http://localhost:80
- Server not yet configured to allow connection from network IP address
google-chrome
edited Sep 17 '13 at 1:49
50-3
3,67931527
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
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,http://localhost:80
- Server not yet configured to allow connection from network IP address
google-chrome
google-chrome
edited Sep 17 '13 at 1:49
50-3
3,67931527
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
edited Sep 17 '13 at 1:49
50-3
3,67931527
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
edited Sep 17 '13 at 1:49
50-3
3,67931527
edited Sep 17 '13 at 1:49
50-3
3,67931527
edited Sep 17 '13 at 1:49
50-3
3,67931527
3,67931527
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
asked Sep 17 '13 at 0:12
EcomEvoEcomEvo
5122620
5122620
The answer on this SO Q&A stackoverflow.com/questions/30467573/… is what worked for me. You need to clear out Chrome's DNS cache through this internal Chrome URL - chrome://net-internals/#dns.
– slm
Apr 19 '18 at 1:50
add a comment |
The answer on this SO Q&A stackoverflow.com/questions/30467573/… is what worked for me. You need to clear out Chrome's DNS cache through this internal Chrome URL - chrome://net-internals/#dns.
– slm
Apr 19 '18 at 1:50
The answer on this SO Q&A stackoverflow.com/questions/30467573/… is what worked for me. You need to clear out Chrome's DNS cache through this internal Chrome URL - chrome://net-internals/#dns.
– slm
Apr 19 '18 at 1:50
The answer on this SO Q&A stackoverflow.com/questions/30467573/… is what worked for me. You need to clear out Chrome's DNS cache through this internal Chrome URL - chrome://net-internals/#dns.
– slm
Apr 19 '18 at 1:50
add a comment |
5 Answers
5
active
oldest
votes
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.
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
12
This no longer works as of now because the mentioned flag is no longer available.
– BullyWiiPlaza
Aug 25 '15 at 11:55
2
@BullyWiiPlaza check chrome://net-internals/#dns because it seems 'Internal DNS client enabled' is set to false by default.
– Alfabravo
Sep 8 '15 at 18:53
@Alfabravo Yes, it is set tofalse
– BullyWiiPlaza
Sep 8 '15 at 19:07
2
My Google Chrome V52 64-bit for Mac had similar problem but chrome://flags had no settings related to DNS. Being desperate I "Reset all settings to default". And then it worked :)
– moshfiqur
Aug 28 '16 at 13:27
I didreset all to default. And now it works. +1
– prashanth
Aug 21 '18 at 11:43
add a comment |
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).
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
Yes ! Work for me changing .dev to .local
– ramiromd
Jan 5 '18 at 14:06
Changing .dev to .test also works for me. Thanks a lot !
– Antoine Subit
Jan 29 '18 at 8:36
add a comment |
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 !
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
1
Doesn't work. Tried this on OSX w/ Chrome 65.0.3325.181.
– slm
Apr 19 '18 at 1:43
add a comment |
@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.
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
add a comment |
This worked for me: suffix the port number
Problem with this URL: http://app.localhost/
Just add the Port number:
Problem solved: http://app.localhost:8000/
Port number will vary based on what you use, XAMPP, APACHE, NGINX, Homestead.
I use Homestead.
answered Apr 9 at 14:06
MotsManishMotsManish
1012
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
protected by Community♦ 22 hours ago
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
12
This no longer works as of now because the mentioned flag is no longer available.
– BullyWiiPlaza
Aug 25 '15 at 11:55
2
@BullyWiiPlaza check chrome://net-internals/#dns because it seems 'Internal DNS client enabled' is set to false by default.
– Alfabravo
Sep 8 '15 at 18:53
@Alfabravo Yes, it is set tofalse
– BullyWiiPlaza
Sep 8 '15 at 19:07
2
My Google Chrome V52 64-bit for Mac had similar problem but chrome://flags had no settings related to DNS. Being desperate I "Reset all settings to default". And then it worked :)
– moshfiqur
Aug 28 '16 at 13:27
I didreset all to default. And now it works. +1
– prashanth
Aug 21 '18 at 11:43
add a comment |
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.
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
12
This no longer works as of now because the mentioned flag is no longer available.
– BullyWiiPlaza
Aug 25 '15 at 11:55
2
@BullyWiiPlaza check chrome://net-internals/#dns because it seems 'Internal DNS client enabled' is set to false by default.
– Alfabravo
Sep 8 '15 at 18:53
@Alfabravo Yes, it is set tofalse
– BullyWiiPlaza
Sep 8 '15 at 19:07
2
My Google Chrome V52 64-bit for Mac had similar problem but chrome://flags had no settings related to DNS. Being desperate I "Reset all settings to default". And then it worked :)
– moshfiqur
Aug 28 '16 at 13:27
I didreset all to default. And now it works. +1
– prashanth
Aug 21 '18 at 11:43
add a comment |
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.
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
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.
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
edited Sep 24 '13 at 12:19
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
answered Sep 24 '13 at 12:14
EcomEvoEcomEvo
5122620
5122620
12
This no longer works as of now because the mentioned flag is no longer available.
– BullyWiiPlaza
Aug 25 '15 at 11:55
2
@BullyWiiPlaza check chrome://net-internals/#dns because it seems 'Internal DNS client enabled' is set to false by default.
– Alfabravo
Sep 8 '15 at 18:53
@Alfabravo Yes, it is set tofalse
– BullyWiiPlaza
Sep 8 '15 at 19:07
2
My Google Chrome V52 64-bit for Mac had similar problem but chrome://flags had no settings related to DNS. Being desperate I "Reset all settings to default". And then it worked :)
– moshfiqur
Aug 28 '16 at 13:27
I didreset all to default. And now it works. +1
– prashanth
Aug 21 '18 at 11:43
add a comment |
12
This no longer works as of now because the mentioned flag is no longer available.
– BullyWiiPlaza
Aug 25 '15 at 11:55
2
@BullyWiiPlaza check chrome://net-internals/#dns because it seems 'Internal DNS client enabled' is set to false by default.
– Alfabravo
Sep 8 '15 at 18:53
@Alfabravo Yes, it is set tofalse
– BullyWiiPlaza
Sep 8 '15 at 19:07
2
My Google Chrome V52 64-bit for Mac had similar problem but chrome://flags had no settings related to DNS. Being desperate I "Reset all settings to default". And then it worked :)
– moshfiqur
Aug 28 '16 at 13:27
I didreset all to default. And now it works. +1
– prashanth
Aug 21 '18 at 11:43
12
12
This no longer works as of now because the mentioned flag is no longer available.
– BullyWiiPlaza
Aug 25 '15 at 11:55
This no longer works as of now because the mentioned flag is no longer available.
– BullyWiiPlaza
Aug 25 '15 at 11:55
2
2
@BullyWiiPlaza check chrome://net-internals/#dns because it seems 'Internal DNS client enabled' is set to false by default.
– Alfabravo
Sep 8 '15 at 18:53
@BullyWiiPlaza check chrome://net-internals/#dns because it seems 'Internal DNS client enabled' is set to false by default.
– Alfabravo
Sep 8 '15 at 18:53
@Alfabravo Yes, it is set to
false– BullyWiiPlaza
Sep 8 '15 at 19:07
@Alfabravo Yes, it is set to
false– BullyWiiPlaza
Sep 8 '15 at 19:07
2
2
My Google Chrome V52 64-bit for Mac had similar problem but chrome://flags had no settings related to DNS. Being desperate I "Reset all settings to default". And then it worked :)
– moshfiqur
Aug 28 '16 at 13:27
My Google Chrome V52 64-bit for Mac had similar problem but chrome://flags had no settings related to DNS. Being desperate I "Reset all settings to default". And then it worked :)
– moshfiqur
Aug 28 '16 at 13:27
I did
reset all to default. And now it works. +1– prashanth
Aug 21 '18 at 11:43
I did
reset all to default. And now it works. +1– prashanth
Aug 21 '18 at 11:43
add a comment |
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).
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
Yes ! Work for me changing .dev to .local
– ramiromd
Jan 5 '18 at 14:06
Changing .dev to .test also works for me. Thanks a lot !
– Antoine Subit
Jan 29 '18 at 8:36
add a comment |
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).
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
Yes ! Work for me changing .dev to .local
– ramiromd
Jan 5 '18 at 14:06
Changing .dev to .test also works for me. Thanks a lot !
– Antoine Subit
Jan 29 '18 at 8:36
add a comment |
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).
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
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).
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
answered Dec 20 '17 at 18:08
Regular JoeRegular Joe
20619
20619
Yes ! Work for me changing .dev to .local
– ramiromd
Jan 5 '18 at 14:06
Changing .dev to .test also works for me. Thanks a lot !
– Antoine Subit
Jan 29 '18 at 8:36
add a comment |
Yes ! Work for me changing .dev to .local
– ramiromd
Jan 5 '18 at 14:06
Changing .dev to .test also works for me. Thanks a lot !
– Antoine Subit
Jan 29 '18 at 8:36
Yes ! Work for me changing .dev to .local
– ramiromd
Jan 5 '18 at 14:06
Yes ! Work for me changing .dev to .local
– ramiromd
Jan 5 '18 at 14:06
Changing .dev to .test also works for me. Thanks a lot !
– Antoine Subit
Jan 29 '18 at 8:36
Changing .dev to .test also works for me. Thanks a lot !
– Antoine Subit
Jan 29 '18 at 8:36
add a comment |
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 !
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
1
Doesn't work. Tried this on OSX w/ Chrome 65.0.3325.181.
– slm
Apr 19 '18 at 1:43
add a comment |
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 !
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
1
Doesn't work. Tried this on OSX w/ Chrome 65.0.3325.181.
– slm
Apr 19 '18 at 1:43
add a comment |
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 !
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
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 !
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
answered Dec 18 '16 at 15:11
Just MeJust Me
1819
1819
1
Doesn't work. Tried this on OSX w/ Chrome 65.0.3325.181.
– slm
Apr 19 '18 at 1:43
add a comment |
1
Doesn't work. Tried this on OSX w/ Chrome 65.0.3325.181.
– slm
Apr 19 '18 at 1:43
1
1
Doesn't work. Tried this on OSX w/ Chrome 65.0.3325.181.
– slm
Apr 19 '18 at 1:43
Doesn't work. Tried this on OSX w/ Chrome 65.0.3325.181.
– slm
Apr 19 '18 at 1:43
add a comment |
@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.
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
add a comment |
@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.
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
add a comment |
@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.
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
@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.
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
answered Feb 1 '18 at 5:05
RPh_CoderRPh_Coder
37834
37834
add a comment |
add a comment |
This worked for me: suffix the port number
Problem with this URL: http://app.localhost/
Just add the Port number:
Problem solved: http://app.localhost:8000/
Port number will vary based on what you use, XAMPP, APACHE, NGINX, Homestead.
I use Homestead.
answered Apr 9 at 14:06
MotsManishMotsManish
1012
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This worked for me: suffix the port number
Problem with this URL: http://app.localhost/
Just add the Port number:
Problem solved: http://app.localhost:8000/
Port number will vary based on what you use, XAMPP, APACHE, NGINX, Homestead.
I use Homestead.
answered Apr 9 at 14:06
MotsManishMotsManish
1012
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This worked for me: suffix the port number
Problem with this URL: http://app.localhost/
Just add the Port number:
Problem solved: http://app.localhost:8000/
Port number will vary based on what you use, XAMPP, APACHE, NGINX, Homestead.
I use Homestead.
answered Apr 9 at 14:06
MotsManishMotsManish
1012
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This worked for me: suffix the port number
Problem with this URL: http://app.localhost/
Just add the Port number:
Problem solved: http://app.localhost:8000/
Port number will vary based on what you use, XAMPP, APACHE, NGINX, Homestead.
I use Homestead.
answered Apr 9 at 14:06
MotsManishMotsManish
1012
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 9 at 14:06
MotsManishMotsManish
1012
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 9 at 14:06
MotsManishMotsManish
1012
answered Apr 9 at 14:06
MotsManishMotsManish
1012
1012
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
MotsManish is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
protected by Community♦ 22 hours ago
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
The answer on this SO Q&A stackoverflow.com/questions/30467573/… is what worked for me. You need to clear out Chrome's DNS cache through this internal Chrome URL - chrome://net-internals/#dns.
– slm
Apr 19 '18 at 1:50