Mixing
WebStorm debugging Angular CLI app points to localhost:63276
I have an Angular app that I am running via the Angular CLI. I am following the steps listed in JetBrains documentation for debugging an Angular CLI app listed here. When I launch DEBUG mode a new browser opens to about:blank instead of http://localhost:4200 as I had specified in the debug configuration. Also when I look at the debugger tab within WebStorm I see the following ...
Why is WebStorm trying to connect to localhost:63276 when I specified localhost:4200 as the start URL in WebStorm debug configuration?
EDIT: I should mention that in the debug configuration I specify the Chrome browser should use my specified user settings so I have access to LastPass and other browser extensions while debugging
angular debugging webstorm
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
add a comment |
I have an Angular app that I am running via the Angular CLI. I am following the steps listed in JetBrains documentation for debugging an Angular CLI app listed here. When I launch DEBUG mode a new browser opens to about:blank instead of http://localhost:4200 as I had specified in the debug configuration. Also when I look at the debugger tab within WebStorm I see the following ...
Why is WebStorm trying to connect to localhost:63276 when I specified localhost:4200 as the start URL in WebStorm debug configuration?
EDIT: I should mention that in the debug configuration I specify the Chrome browser should use my specified user settings so I have access to LastPass and other browser extensions while debugging
angular debugging webstorm
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
add a comment |
I have an Angular app that I am running via the Angular CLI. I am following the steps listed in JetBrains documentation for debugging an Angular CLI app listed here. When I launch DEBUG mode a new browser opens to about:blank instead of http://localhost:4200 as I had specified in the debug configuration. Also when I look at the debugger tab within WebStorm I see the following ...
Why is WebStorm trying to connect to localhost:63276 when I specified localhost:4200 as the start URL in WebStorm debug configuration?
EDIT: I should mention that in the debug configuration I specify the Chrome browser should use my specified user settings so I have access to LastPass and other browser extensions while debugging
angular debugging webstorm
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
I have an Angular app that I am running via the Angular CLI. I am following the steps listed in JetBrains documentation for debugging an Angular CLI app listed here. When I launch DEBUG mode a new browser opens to about:blank instead of http://localhost:4200 as I had specified in the debug configuration. Also when I look at the debugger tab within WebStorm I see the following ...
Why is WebStorm trying to connect to localhost:63276 when I specified localhost:4200 as the start URL in WebStorm debug configuration?
EDIT: I should mention that in the debug configuration I specify the Chrome browser should use my specified user settings so I have access to LastPass and other browser extensions while debugging
angular debugging webstorm
angular debugging webstorm
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
edited Nov 19 '18 at 21:44
webworm
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
asked Nov 19 '18 at 21:39
webwormwebworm
4,2122080147
4,2122080147
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
63276 is the port debugger is started on, it should not match the port your server is listening on.
Please make sure to close all running Chrome instances prior to starting the debugger - as it's written in the error message, debug port can't be opened if you have a running Chrome with your user data. See https://www.jetbrains.com/help/webstorm/configuring-javascript-debugger.html#ws_js_debug_default_chrome_user_data:
To open a new Chrome instance with your familiar look-and-feel, configure Chrome in WebStorm to start with your user data. In this case, before starting a debugging session, always make sure that Chrome is not already running with your user data. Otherwise WebStorm still launches another instance of Chrome with your user data but is unable to open a debugging port for it. As a result, WebStorm debugger fails to connect to the application in the new Chrome instance and the debugging session does not start.
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
Thank you. That solved the issue. I just had to make sure I did not have another Chrome instance already open. I have my API server on the same machine and it had opened a Chrome instance itself when started.Solution was to start the Angular app first then launch the API server.
– webworm
Nov 20 '18 at 21:30
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383015%2fwebstorm-debugging-angular-cli-app-points-to-localhost63276%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
63276 is the port debugger is started on, it should not match the port your server is listening on.
Please make sure to close all running Chrome instances prior to starting the debugger - as it's written in the error message, debug port can't be opened if you have a running Chrome with your user data. See https://www.jetbrains.com/help/webstorm/configuring-javascript-debugger.html#ws_js_debug_default_chrome_user_data:
To open a new Chrome instance with your familiar look-and-feel, configure Chrome in WebStorm to start with your user data. In this case, before starting a debugging session, always make sure that Chrome is not already running with your user data. Otherwise WebStorm still launches another instance of Chrome with your user data but is unable to open a debugging port for it. As a result, WebStorm debugger fails to connect to the application in the new Chrome instance and the debugging session does not start.
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
Thank you. That solved the issue. I just had to make sure I did not have another Chrome instance already open. I have my API server on the same machine and it had opened a Chrome instance itself when started.Solution was to start the Angular app first then launch the API server.
– webworm
Nov 20 '18 at 21:30
add a comment |
63276 is the port debugger is started on, it should not match the port your server is listening on.
Please make sure to close all running Chrome instances prior to starting the debugger - as it's written in the error message, debug port can't be opened if you have a running Chrome with your user data. See https://www.jetbrains.com/help/webstorm/configuring-javascript-debugger.html#ws_js_debug_default_chrome_user_data:
To open a new Chrome instance with your familiar look-and-feel, configure Chrome in WebStorm to start with your user data. In this case, before starting a debugging session, always make sure that Chrome is not already running with your user data. Otherwise WebStorm still launches another instance of Chrome with your user data but is unable to open a debugging port for it. As a result, WebStorm debugger fails to connect to the application in the new Chrome instance and the debugging session does not start.
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
Thank you. That solved the issue. I just had to make sure I did not have another Chrome instance already open. I have my API server on the same machine and it had opened a Chrome instance itself when started.Solution was to start the Angular app first then launch the API server.
– webworm
Nov 20 '18 at 21:30
add a comment |
63276 is the port debugger is started on, it should not match the port your server is listening on.
Please make sure to close all running Chrome instances prior to starting the debugger - as it's written in the error message, debug port can't be opened if you have a running Chrome with your user data. See https://www.jetbrains.com/help/webstorm/configuring-javascript-debugger.html#ws_js_debug_default_chrome_user_data:
To open a new Chrome instance with your familiar look-and-feel, configure Chrome in WebStorm to start with your user data. In this case, before starting a debugging session, always make sure that Chrome is not already running with your user data. Otherwise WebStorm still launches another instance of Chrome with your user data but is unable to open a debugging port for it. As a result, WebStorm debugger fails to connect to the application in the new Chrome instance and the debugging session does not start.
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
63276 is the port debugger is started on, it should not match the port your server is listening on.
Please make sure to close all running Chrome instances prior to starting the debugger - as it's written in the error message, debug port can't be opened if you have a running Chrome with your user data. See https://www.jetbrains.com/help/webstorm/configuring-javascript-debugger.html#ws_js_debug_default_chrome_user_data:
To open a new Chrome instance with your familiar look-and-feel, configure Chrome in WebStorm to start with your user data. In this case, before starting a debugging session, always make sure that Chrome is not already running with your user data. Otherwise WebStorm still launches another instance of Chrome with your user data but is unable to open a debugging port for it. As a result, WebStorm debugger fails to connect to the application in the new Chrome instance and the debugging session does not start.
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
answered Nov 20 '18 at 12:38
lenalena
50.9k37380
50.9k37380
Thank you. That solved the issue. I just had to make sure I did not have another Chrome instance already open. I have my API server on the same machine and it had opened a Chrome instance itself when started.Solution was to start the Angular app first then launch the API server.
– webworm
Nov 20 '18 at 21:30
add a comment |
Thank you. That solved the issue. I just had to make sure I did not have another Chrome instance already open. I have my API server on the same machine and it had opened a Chrome instance itself when started.Solution was to start the Angular app first then launch the API server.
– webworm
Nov 20 '18 at 21:30
Thank you. That solved the issue. I just had to make sure I did not have another Chrome instance already open. I have my API server on the same machine and it had opened a Chrome instance itself when started.Solution was to start the Angular app first then launch the API server.
– webworm
Nov 20 '18 at 21:30
Thank you. That solved the issue. I just had to make sure I did not have another Chrome instance already open. I have my API server on the same machine and it had opened a Chrome instance itself when started.Solution was to start the Angular app first then launch the API server.
– webworm
Nov 20 '18 at 21:30
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383015%2fwebstorm-debugging-angular-cli-app-points-to-localhost63276%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
