Any angular app is not running on any browser
up vote
-5
down vote
favorite
localhost took too long to respond...ERR_CONNECTION_TIME_OUT
- Any Angular app is not running on any browser.
- Tried to uninstall it and clean the cache again install it but it doesn't work either.
- Update package.json too console shows that compiled successfully.
angular
edited Nov 10 at 18:22
georgeawg
31.9k104863
asked Nov 10 at 14:36
Helly Thakkar
31
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
|
show 3 more comments
up vote
-5
down vote
favorite
localhost took too long to respond...ERR_CONNECTION_TIME_OUT
- Any Angular app is not running on any browser.
- Tried to uninstall it and clean the cache again install it but it doesn't work either.
- Update package.json too console shows that compiled successfully.
angular
edited Nov 10 at 18:22
georgeawg
31.9k104863
asked Nov 10 at 14:36
Helly Thakkar
31
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hi Helly, welcome to stackoverflow. You have tagged the question for both angular and angularjs. Just in case if you are not aware, both are completely different and may attract attention from audience with a completely different skill set.
– Sachin Gupta
Nov 10 at 15:28
Can you please update the answer to include some steps on how you reached this error and how you are trying to run the app.
– Sachin Gupta
Nov 10 at 15:29
With these information, one can only guess what you did. This looks like you're somehow terminating your development server - but as already mentioned, please provide your exact steps that lead to thos problem (what commands are your running, what is the output on terminal, etc)
– pascalpuetz
Nov 10 at 16:44
If your'e using angular-cli, Are you write ng serve in a console in the application folder before ask for localhost:4200 in navigator ?
– Eliseo
Nov 10 at 17:53
What is your terminal input and output? What do you write on your console and what exactly does it say? To start the development server, please mind that the correct command is, as mentioned, ng serve and not ng build!
– pascalpuetz
Nov 10 at 20:47
|
show 3 more comments
up vote
-5
down vote
favorite
up vote
-5
down vote
favorite
localhost took too long to respond...ERR_CONNECTION_TIME_OUT
- Any Angular app is not running on any browser.
- Tried to uninstall it and clean the cache again install it but it doesn't work either.
- Update package.json too console shows that compiled successfully.
angular
edited Nov 10 at 18:22
georgeawg
31.9k104863
asked Nov 10 at 14:36
Helly Thakkar
31
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
localhost took too long to respond...ERR_CONNECTION_TIME_OUT
- Any Angular app is not running on any browser.
- Tried to uninstall it and clean the cache again install it but it doesn't work either.
- Update package.json too console shows that compiled successfully.
angular
angular
edited Nov 10 at 18:22
georgeawg
31.9k104863
asked Nov 10 at 14:36
Helly Thakkar
31
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 10 at 18:22
georgeawg
31.9k104863
asked Nov 10 at 14:36
Helly Thakkar
31
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 10 at 18:22
georgeawg
31.9k104863
edited Nov 10 at 18:22
georgeawg
31.9k104863
edited Nov 10 at 18:22
georgeawg
31.9k104863
31.9k104863
asked Nov 10 at 14:36
Helly Thakkar
31
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 10 at 14:36
Helly Thakkar
31
asked Nov 10 at 14:36
Helly Thakkar
31
31
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Helly Thakkar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hi Helly, welcome to stackoverflow. You have tagged the question for both angular and angularjs. Just in case if you are not aware, both are completely different and may attract attention from audience with a completely different skill set.
– Sachin Gupta
Nov 10 at 15:28
Can you please update the answer to include some steps on how you reached this error and how you are trying to run the app.
– Sachin Gupta
Nov 10 at 15:29
With these information, one can only guess what you did. This looks like you're somehow terminating your development server - but as already mentioned, please provide your exact steps that lead to thos problem (what commands are your running, what is the output on terminal, etc)
– pascalpuetz
Nov 10 at 16:44
If your'e using angular-cli, Are you write ng serve in a console in the application folder before ask for localhost:4200 in navigator ?
– Eliseo
Nov 10 at 17:53
What is your terminal input and output? What do you write on your console and what exactly does it say? To start the development server, please mind that the correct command is, as mentioned, ng serve and not ng build!
– pascalpuetz
Nov 10 at 20:47
|
show 3 more comments
Hi Helly, welcome to stackoverflow. You have tagged the question for both angular and angularjs. Just in case if you are not aware, both are completely different and may attract attention from audience with a completely different skill set.
– Sachin Gupta
Nov 10 at 15:28
Can you please update the answer to include some steps on how you reached this error and how you are trying to run the app.
– Sachin Gupta
Nov 10 at 15:29
With these information, one can only guess what you did. This looks like you're somehow terminating your development server - but as already mentioned, please provide your exact steps that lead to thos problem (what commands are your running, what is the output on terminal, etc)
– pascalpuetz
Nov 10 at 16:44
If your'e using angular-cli, Are you write ng serve in a console in the application folder before ask for localhost:4200 in navigator ?
– Eliseo
Nov 10 at 17:53
What is your terminal input and output? What do you write on your console and what exactly does it say? To start the development server, please mind that the correct command is, as mentioned, ng serve and not ng build!
– pascalpuetz
Nov 10 at 20:47
Hi Helly, welcome to stackoverflow. You have tagged the question for both angular and angularjs. Just in case if you are not aware, both are completely different and may attract attention from audience with a completely different skill set.
– Sachin Gupta
Nov 10 at 15:28
Hi Helly, welcome to stackoverflow. You have tagged the question for both angular and angularjs. Just in case if you are not aware, both are completely different and may attract attention from audience with a completely different skill set.
– Sachin Gupta
Nov 10 at 15:28
Can you please update the answer to include some steps on how you reached this error and how you are trying to run the app.
– Sachin Gupta
Nov 10 at 15:29
Can you please update the answer to include some steps on how you reached this error and how you are trying to run the app.
– Sachin Gupta
Nov 10 at 15:29
With these information, one can only guess what you did. This looks like you're somehow terminating your development server - but as already mentioned, please provide your exact steps that lead to thos problem (what commands are your running, what is the output on terminal, etc)
– pascalpuetz
Nov 10 at 16:44
With these information, one can only guess what you did. This looks like you're somehow terminating your development server - but as already mentioned, please provide your exact steps that lead to thos problem (what commands are your running, what is the output on terminal, etc)
– pascalpuetz
Nov 10 at 16:44
If your'e using angular-cli, Are you write ng serve in a console in the application folder before ask for localhost:4200 in navigator ?
– Eliseo
Nov 10 at 17:53
If your'e using angular-cli, Are you write ng serve in a console in the application folder before ask for localhost:4200 in navigator ?
– Eliseo
Nov 10 at 17:53
What is your terminal input and output? What do you write on your console and what exactly does it say? To start the development server, please mind that the correct command is, as mentioned, ng serve and not ng build!
– pascalpuetz
Nov 10 at 20:47
What is your terminal input and output? What do you write on your console and what exactly does it say? To start the development server, please mind that the correct command is, as mentioned, ng serve and not ng build!
– pascalpuetz
Nov 10 at 20:47
|
show 3 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
With the provided information, it is difficult to analyze the problem.
Still, I will try to give you a few hints on what may be the problem in your case.
- Check if you are running the correct command. If you are using the angular cli, the correct command to start a development server is
ng serve
- Check if you are opening the correct port. The default port is
4200, but depending on your configuration this might not be the case. To be 100% sure runng serve --port=4200
- Make sure that nothing is blocking the selected port. Usually, the cli will throw an error message if the port is blocked. Again, to make sure, either run the appropriate command for your OS to check if the selected port is blocked or just try a different port (e.g.
ng serve --port=5678) and open your browser at that adress. - If you are behind a corporate proxy or VPN of some kind, add localhost to your NO_PROXY environment variable. This should usually not be a problem, but you never know with corporate proxies.
Again, it would be really helpful if you further provided the console outputs.
answered Nov 10 at 20:59
pascalpuetz
31118
Date: 2018-11-11T10:50:21.600Z Hash: 07ab1847afafcf0fed6f Time: 10582ms chunk {main} main.js, main.js.map (main) 12.7 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 16.2 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 3.55 MB [initial] [rendered] i ｢wdm｣: Compiled successfully.
– Helly Thakkar
2 days ago
again facing the same problems ..tried everything which is mentioned in your hint..and thank you for helping..!!
– Helly Thakkar
2 days ago
Did the output say something like 'development server started on port...'?
– pascalpuetz
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
With the provided information, it is difficult to analyze the problem.
Still, I will try to give you a few hints on what may be the problem in your case.
- Check if you are running the correct command. If you are using the angular cli, the correct command to start a development server is
ng serve
- Check if you are opening the correct port. The default port is
4200, but depending on your configuration this might not be the case. To be 100% sure runng serve --port=4200
- Make sure that nothing is blocking the selected port. Usually, the cli will throw an error message if the port is blocked. Again, to make sure, either run the appropriate command for your OS to check if the selected port is blocked or just try a different port (e.g.
ng serve --port=5678) and open your browser at that adress. - If you are behind a corporate proxy or VPN of some kind, add localhost to your NO_PROXY environment variable. This should usually not be a problem, but you never know with corporate proxies.
Again, it would be really helpful if you further provided the console outputs.
answered Nov 10 at 20:59
pascalpuetz
31118
Date: 2018-11-11T10:50:21.600Z Hash: 07ab1847afafcf0fed6f Time: 10582ms chunk {main} main.js, main.js.map (main) 12.7 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 16.2 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 3.55 MB [initial] [rendered] i ｢wdm｣: Compiled successfully.
– Helly Thakkar
2 days ago
again facing the same problems ..tried everything which is mentioned in your hint..and thank you for helping..!!
– Helly Thakkar
2 days ago
Did the output say something like 'development server started on port...'?
– pascalpuetz
2 days ago
add a comment |
up vote
0
down vote
accepted
With the provided information, it is difficult to analyze the problem.
Still, I will try to give you a few hints on what may be the problem in your case.
- Check if you are running the correct command. If you are using the angular cli, the correct command to start a development server is
ng serve
- Check if you are opening the correct port. The default port is
4200, but depending on your configuration this might not be the case. To be 100% sure runng serve --port=4200
- Make sure that nothing is blocking the selected port. Usually, the cli will throw an error message if the port is blocked. Again, to make sure, either run the appropriate command for your OS to check if the selected port is blocked or just try a different port (e.g.
ng serve --port=5678) and open your browser at that adress. - If you are behind a corporate proxy or VPN of some kind, add localhost to your NO_PROXY environment variable. This should usually not be a problem, but you never know with corporate proxies.
Again, it would be really helpful if you further provided the console outputs.
answered Nov 10 at 20:59
pascalpuetz
31118
Date: 2018-11-11T10:50:21.600Z Hash: 07ab1847afafcf0fed6f Time: 10582ms chunk {main} main.js, main.js.map (main) 12.7 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 16.2 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 3.55 MB [initial] [rendered] i ｢wdm｣: Compiled successfully.
– Helly Thakkar
2 days ago
again facing the same problems ..tried everything which is mentioned in your hint..and thank you for helping..!!
– Helly Thakkar
2 days ago
Did the output say something like 'development server started on port...'?
– pascalpuetz
2 days ago
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
With the provided information, it is difficult to analyze the problem.
Still, I will try to give you a few hints on what may be the problem in your case.
- Check if you are running the correct command. If you are using the angular cli, the correct command to start a development server is
ng serve
- Check if you are opening the correct port. The default port is
4200, but depending on your configuration this might not be the case. To be 100% sure runng serve --port=4200
- Make sure that nothing is blocking the selected port. Usually, the cli will throw an error message if the port is blocked. Again, to make sure, either run the appropriate command for your OS to check if the selected port is blocked or just try a different port (e.g.
ng serve --port=5678) and open your browser at that adress. - If you are behind a corporate proxy or VPN of some kind, add localhost to your NO_PROXY environment variable. This should usually not be a problem, but you never know with corporate proxies.
Again, it would be really helpful if you further provided the console outputs.
answered Nov 10 at 20:59
pascalpuetz
31118
With the provided information, it is difficult to analyze the problem.
Still, I will try to give you a few hints on what may be the problem in your case.
- Check if you are running the correct command. If you are using the angular cli, the correct command to start a development server is
ng serve
- Check if you are opening the correct port. The default port is
4200, but depending on your configuration this might not be the case. To be 100% sure runng serve --port=4200
- Make sure that nothing is blocking the selected port. Usually, the cli will throw an error message if the port is blocked. Again, to make sure, either run the appropriate command for your OS to check if the selected port is blocked or just try a different port (e.g.
ng serve --port=5678) and open your browser at that adress. - If you are behind a corporate proxy or VPN of some kind, add localhost to your NO_PROXY environment variable. This should usually not be a problem, but you never know with corporate proxies.
Again, it would be really helpful if you further provided the console outputs.
answered Nov 10 at 20:59
pascalpuetz
31118
answered Nov 10 at 20:59
pascalpuetz
31118
answered Nov 10 at 20:59
pascalpuetz
31118
answered Nov 10 at 20:59
pascalpuetz
31118
31118
Date: 2018-11-11T10:50:21.600Z Hash: 07ab1847afafcf0fed6f Time: 10582ms chunk {main} main.js, main.js.map (main) 12.7 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 16.2 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 3.55 MB [initial] [rendered] i ｢wdm｣: Compiled successfully.
– Helly Thakkar
2 days ago
again facing the same problems ..tried everything which is mentioned in your hint..and thank you for helping..!!
– Helly Thakkar
2 days ago
Did the output say something like 'development server started on port...'?
– pascalpuetz
2 days ago
add a comment |
Date: 2018-11-11T10:50:21.600Z Hash: 07ab1847afafcf0fed6f Time: 10582ms chunk {main} main.js, main.js.map (main) 12.7 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 16.2 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 3.55 MB [initial] [rendered] i ｢wdm｣: Compiled successfully.
– Helly Thakkar
2 days ago
again facing the same problems ..tried everything which is mentioned in your hint..and thank you for helping..!!
– Helly Thakkar
2 days ago
Did the output say something like 'development server started on port...'?
– pascalpuetz
2 days ago
Date: 2018-11-11T10:50:21.600Z Hash: 07ab1847afafcf0fed6f Time: 10582ms chunk {main} main.js, main.js.map (main) 12.7 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 16.2 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 3.55 MB [initial] [rendered] i ｢wdm｣: Compiled successfully.
– Helly Thakkar
2 days ago
Date: 2018-11-11T10:50:21.600Z Hash: 07ab1847afafcf0fed6f Time: 10582ms chunk {main} main.js, main.js.map (main) 12.7 kB [initial] [rendered] chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 223 kB [initial] [rendered] chunk {runtime} runtime.js, runtime.js.map (runtime) 6.08 kB [entry] [rendered] chunk {styles} styles.js, styles.js.map (styles) 16.2 kB [initial] [rendered] chunk {vendor} vendor.js, vendor.js.map (vendor) 3.55 MB [initial] [rendered] i ｢wdm｣: Compiled successfully.
– Helly Thakkar
2 days ago
again facing the same problems ..tried everything which is mentioned in your hint..and thank you for helping..!!
– Helly Thakkar
2 days ago
again facing the same problems ..tried everything which is mentioned in your hint..and thank you for helping..!!
– Helly Thakkar
2 days ago
Did the output say something like 'development server started on port...'?
– pascalpuetz
2 days ago
Did the output say something like 'development server started on port...'?
– pascalpuetz
2 days ago
add a comment |
Helly Thakkar is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Helly Thakkar is a new contributor. Be nice, and check out our Code of Conduct.
Helly Thakkar is a new contributor. Be nice, and check out our Code of Conduct.
Helly Thakkar is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239991%2fany-angular-app-is-not-running-on-any-browser%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Hi Helly, welcome to stackoverflow. You have tagged the question for both angular and angularjs. Just in case if you are not aware, both are completely different and may attract attention from audience with a completely different skill set.
– Sachin Gupta
Nov 10 at 15:28
Can you please update the answer to include some steps on how you reached this error and how you are trying to run the app.
– Sachin Gupta
Nov 10 at 15:29
With these information, one can only guess what you did. This looks like you're somehow terminating your development server - but as already mentioned, please provide your exact steps that lead to thos problem (what commands are your running, what is the output on terminal, etc)
– pascalpuetz
Nov 10 at 16:44
If your'e using angular-cli, Are you write ng serve in a console in the application folder before ask for localhost:4200 in navigator ?
– Eliseo
Nov 10 at 17:53
What is your terminal input and output? What do you write on your console and what exactly does it say? To start the development server, please mind that the correct command is, as mentioned, ng serve and not ng build!
– pascalpuetz
Nov 10 at 20:47