How to kill a localhost:8080
I'm trying to kill a dev server setup via yarn. While I Ctrl+C'd the command prompt, when I went back to localhost:8080
it had not stopped. How can I kill the process?
windows localhost
New contributor
add a comment |
I'm trying to kill a dev server setup via yarn. While I Ctrl+C'd the command prompt, when I went back to localhost:8080
it had not stopped. How can I kill the process?
windows localhost
New contributor
Just double checking but is this issue happening on a Windows machine?
– JakeGould
5 hours ago
@JakeGould Yes it is.
– Sam
4 hours ago
add a comment |
I'm trying to kill a dev server setup via yarn. While I Ctrl+C'd the command prompt, when I went back to localhost:8080
it had not stopped. How can I kill the process?
windows localhost
New contributor
I'm trying to kill a dev server setup via yarn. While I Ctrl+C'd the command prompt, when I went back to localhost:8080
it had not stopped. How can I kill the process?
windows localhost
windows localhost
New contributor
New contributor
edited 5 hours ago
JakeGould
31.6k1097139
31.6k1097139
New contributor
asked 5 hours ago
SamSam
183
183
New contributor
New contributor
Just double checking but is this issue happening on a Windows machine?
– JakeGould
5 hours ago
@JakeGould Yes it is.
– Sam
4 hours ago
add a comment |
Just double checking but is this issue happening on a Windows machine?
– JakeGould
5 hours ago
@JakeGould Yes it is.
– Sam
4 hours ago
Just double checking but is this issue happening on a Windows machine?
– JakeGould
5 hours ago
Just double checking but is this issue happening on a Windows machine?
– JakeGould
5 hours ago
@JakeGould Yes it is.
– Sam
4 hours ago
@JakeGould Yes it is.
– Sam
4 hours ago
add a comment |
1 Answer
1
active
oldest
votes
You can track down the process running on port 8080 and kill it.
For macOS or Linux:
sudo lsof -iTCP:8080 -sTCP:LISTEN
You should get an output something like:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
yarn 12017 user 12u IPv6 1876683 0t0 TCP *:8080 (LISTEN)
Now that you have the process ID(PID), you can kill the process. First try:
kill 12017(whatever the PID is)
If that does nothing, try:
kill -9 12017
For Windows:
netstat -ano | findstr :8080 (the port number)
This should give you the process to kill. You can then run:
taskkill /F /PID 12017(or whatever the process ID is)
1
This is a decent answer. But the original poster has trigged this question as a Windows related question. Would this still work?
– JakeGould
5 hours ago
@JakeGould took my words right out of my own mouth. Would this work on windows?
– Sam
5 hours ago
1
Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating
– baelx
5 hours ago
2
Thank you. This solved the problem perfectly.
– Sam
4 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
Sam is a new contributor. Be nice, and check out our Code of Conduct.
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%2fsuperuser.com%2fquestions%2f1411293%2fhow-to-kill-a-localhost8080%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
You can track down the process running on port 8080 and kill it.
For macOS or Linux:
sudo lsof -iTCP:8080 -sTCP:LISTEN
You should get an output something like:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
yarn 12017 user 12u IPv6 1876683 0t0 TCP *:8080 (LISTEN)
Now that you have the process ID(PID), you can kill the process. First try:
kill 12017(whatever the PID is)
If that does nothing, try:
kill -9 12017
For Windows:
netstat -ano | findstr :8080 (the port number)
This should give you the process to kill. You can then run:
taskkill /F /PID 12017(or whatever the process ID is)
1
This is a decent answer. But the original poster has trigged this question as a Windows related question. Would this still work?
– JakeGould
5 hours ago
@JakeGould took my words right out of my own mouth. Would this work on windows?
– Sam
5 hours ago
1
Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating
– baelx
5 hours ago
2
Thank you. This solved the problem perfectly.
– Sam
4 hours ago
add a comment |
You can track down the process running on port 8080 and kill it.
For macOS or Linux:
sudo lsof -iTCP:8080 -sTCP:LISTEN
You should get an output something like:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
yarn 12017 user 12u IPv6 1876683 0t0 TCP *:8080 (LISTEN)
Now that you have the process ID(PID), you can kill the process. First try:
kill 12017(whatever the PID is)
If that does nothing, try:
kill -9 12017
For Windows:
netstat -ano | findstr :8080 (the port number)
This should give you the process to kill. You can then run:
taskkill /F /PID 12017(or whatever the process ID is)
1
This is a decent answer. But the original poster has trigged this question as a Windows related question. Would this still work?
– JakeGould
5 hours ago
@JakeGould took my words right out of my own mouth. Would this work on windows?
– Sam
5 hours ago
1
Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating
– baelx
5 hours ago
2
Thank you. This solved the problem perfectly.
– Sam
4 hours ago
add a comment |
You can track down the process running on port 8080 and kill it.
For macOS or Linux:
sudo lsof -iTCP:8080 -sTCP:LISTEN
You should get an output something like:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
yarn 12017 user 12u IPv6 1876683 0t0 TCP *:8080 (LISTEN)
Now that you have the process ID(PID), you can kill the process. First try:
kill 12017(whatever the PID is)
If that does nothing, try:
kill -9 12017
For Windows:
netstat -ano | findstr :8080 (the port number)
This should give you the process to kill. You can then run:
taskkill /F /PID 12017(or whatever the process ID is)
You can track down the process running on port 8080 and kill it.
For macOS or Linux:
sudo lsof -iTCP:8080 -sTCP:LISTEN
You should get an output something like:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
yarn 12017 user 12u IPv6 1876683 0t0 TCP *:8080 (LISTEN)
Now that you have the process ID(PID), you can kill the process. First try:
kill 12017(whatever the PID is)
If that does nothing, try:
kill -9 12017
For Windows:
netstat -ano | findstr :8080 (the port number)
This should give you the process to kill. You can then run:
taskkill /F /PID 12017(or whatever the process ID is)
edited 4 hours ago
answered 5 hours ago
baelxbaelx
909313
909313
1
This is a decent answer. But the original poster has trigged this question as a Windows related question. Would this still work?
– JakeGould
5 hours ago
@JakeGould took my words right out of my own mouth. Would this work on windows?
– Sam
5 hours ago
1
Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating
– baelx
5 hours ago
2
Thank you. This solved the problem perfectly.
– Sam
4 hours ago
add a comment |
1
This is a decent answer. But the original poster has trigged this question as a Windows related question. Would this still work?
– JakeGould
5 hours ago
@JakeGould took my words right out of my own mouth. Would this work on windows?
– Sam
5 hours ago
1
Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating
– baelx
5 hours ago
2
Thank you. This solved the problem perfectly.
– Sam
4 hours ago
1
1
This is a decent answer. But the original poster has trigged this question as a Windows related question. Would this still work?
– JakeGould
5 hours ago
This is a decent answer. But the original poster has trigged this question as a Windows related question. Would this still work?
– JakeGould
5 hours ago
@JakeGould took my words right out of my own mouth. Would this work on windows?
– Sam
5 hours ago
@JakeGould took my words right out of my own mouth. Would this work on windows?
– Sam
5 hours ago
1
1
Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating
– baelx
5 hours ago
Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating
– baelx
5 hours ago
2
2
Thank you. This solved the problem perfectly.
– Sam
4 hours ago
Thank you. This solved the problem perfectly.
– Sam
4 hours ago
add a comment |
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Sam is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1411293%2fhow-to-kill-a-localhost8080%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
Just double checking but is this issue happening on a Windows machine?
– JakeGould
5 hours ago
@JakeGould Yes it is.
– Sam
4 hours ago