How to kill a localhost:8080Safari is unable to reach localhost (127.0.0.1)Exclude localhost from...
What is the wife of a henpecked husband called?
Did Amazon pay $0 in taxes last year?
Accessing something inside the object when you don't know the key
How to speed up a process
CBP Reminds Travelers to Allow 72 Hours for ESTA. Why?
Six real numbers so that product of any five is the sixth one
Is my plan for fixing my water heater leak bad?
Is there a German word for “analytics”?
Why does the 31P{1H} NMR spectrum of cis-[Mo(CO)2(dppe)2] show two signals?
Use comma instead of & in table
Has the Isbell–Freyd criterion ever been used to check that a category is concretisable?
How to kill a localhost:8080
I am on the US no-fly list. What can I do in order to be allowed on flights which go through US airspace?
Pronunciation of powers
What's the difference between a cart and a wagon?
Is the set of paths between any two points moving only in units on the plane countable or uncountable?
Pure Functions: Does "No Side Effects" Imply "Always Same Output, Given Same Input"?
A "strange" unit radio astronomy
How do I construct an nxn matrix?
Reason Why Dimensional Travelling Would be Restricted
Should I choose Itemized or Standard deduction?
Where is this triangular-shaped space station from?
Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?
Equivalent to "source" in OpenBSD?
How to kill a localhost:8080
Safari is unable to reach localhost (127.0.0.1)Exclude localhost from htt_proxyConnect to localhost from another computerhttp://localhost:8080 is not working on running apacher Server through XAMPPSetting up email for localhostThunderbird configuration for James on localhostWhy I haven't got right to kill a process from Windows' command prompt?Override localhost IP Adress in Windows 8.1Can't kill process with Task Manager or taskkillAccess to local IP on port 3000 works but 8080 does not
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
5 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 6 hours ago
SamSam
233
233
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
5 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
5 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
5 hours ago
@JakeGould Yes it is.
– Sam
5 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
5 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
5 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
5 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 5 hours ago
answered 5 hours ago
baelxbaelx
929313
929313
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
5 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
5 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
5 hours ago
Thank you. This solved the problem perfectly.
– Sam
5 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
5 hours ago