How to kill a localhost:8080Safari is unable to reach localhost (127.0.0.1)How can I kill a process from the...
Center single line(s) in align
Skis versus snow shoes - when to choose which for travelling the backcountry?
How can I be pwned if I'm not registered on the compromised site?
Rationale to prefer local variables over instance variables?
How do ISS astronauts "get their stripes"?
How can atoms be electrically neutral when there is a difference in the positions of the charges?
Why is s'abonner reflexive?
Is it possible to convert a suspension fork to rigid by drilling it?
Second-rate spelling
RS232 to Raspberry Pi Zero W
What happened to QGIS 2.x
Borrowing Characters
In iTunes 12 on macOS, how can I reset the skip count of a song?
How to lift/raise/repair a segment of concrete slab?
Sometimes a banana is just a banana
Forward slip vs side slip
Traversing Africa: A Cryptic Journey
Reason why dimensional travelling would be restricted
Dystopian novel where telepathic humans live under a dome
VAT refund for a conference ticket in Sweden
Can I become debt free or should I file for bankruptcy? How do I manage my debt and finances?
Filling in Area Under Curve Causes Alignment Issues
Non-Italian European mafias in USA?
I can't die. Who am I?
How to kill a localhost:8080
Safari is unable to reach localhost (127.0.0.1)How can I kill a process from the command prompt on Windows NT?Localhost does not respondExclude localhost from htt_proxyhttp://localhost:8080 is not working on running apacher Server through XAMPPWhy I haven't got right to kill a process from Windows' command prompt?Override localhost IP Adress in Windows 8.1Windows - Kill All Non-Essential Running ProcessesCan'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 on Windows. 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
edited 5 hours ago
Run5k
11.3k73152
asked 20 hours ago
SamSam
14825
New contributor
Sam 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 |
I'm trying to kill a dev server setup via yarn on Windows. 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
edited 5 hours ago
Run5k
11.3k73152
asked 20 hours ago
SamSam
14825
New contributor
Sam 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 |
I'm trying to kill a dev server setup via yarn on Windows. 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
edited 5 hours ago
Run5k
11.3k73152
asked 20 hours ago
SamSam
14825
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm trying to kill a dev server setup via yarn on Windows. 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
edited 5 hours ago
Run5k
11.3k73152
asked 20 hours ago
SamSam
14825
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 5 hours ago
Run5k
11.3k73152
asked 20 hours ago
SamSam
14825
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 5 hours ago
Run5k
11.3k73152
edited 5 hours ago
Run5k
11.3k73152
edited 5 hours ago
Run5k
11.3k73152
11.3k73152
asked 20 hours ago
SamSam
14825
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 20 hours ago
SamSam
14825
asked 20 hours ago
SamSam
14825
14825
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Sam is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Sam 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 |
3 Answers
3
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)
answered 20 hours ago
baelxbaelx
1,079615
Wow,-anois yet an other weird Italian mnemonic fornetstatafter-puttana... I wonder if they designed it to yield these explicit references or whether it's just chance.
– Bakuriu
3 hours ago
1
For an 'all in one' linux command, check out fuser.fuser -k 8080/tcp 8080/udpshould kill anything listening on 8080.
– mbrig
3 hours ago
NB: The Windows command will also list all local processes that are connected to the webserver, at the instant that the command was run. The left address:port pair is the source address, the right address:port is the destination. Adding -t tcp will only list TCP connections, not UDP connections
– CSM
1 hour ago
add a comment |
If you install ProcessExplorer from SystemInternals, then you can see the process tree.
In ProcessExplorer, click the target-sight button, and then click on the cmd prompt that you launched the webrowser from. ProcessExplorer will then jump to that cmd prompt in its list. If the process view is not already threaded by parent-child relation, then press Ctrl-T a few times until it is. You then should be able to see the webserver. Select it, and then right-click on it. Select "Kill Process Tree" to forcibly kill the webserver.
SystemInternals also has pskill. You can use pskill -t "MyWebServer" to kill all processes, and their children, than are called MyWebServer.
answered 1 hour ago
CSMCSM
54124
add a comment |
Unless the process you're trying to kill is one that gets started upon booting the server, rebooting the computer in question would probably work. It's probably a last resort option due to losing everything else the computer's been doing that hasn't been saved, and the time it takes for the reboot to occur, but there's a reason why a lot of IT professionals start their troubleshooting process for user machines with "Have you tried turning the computer off and back on again?"
answered 9 hours ago
nick012000nick012000
95
New contributor
nick012000 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 |
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
3 Answers
3
active
oldest
votes
3 Answers
3
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)
answered 20 hours ago
baelxbaelx
1,079615
Wow,-anois yet an other weird Italian mnemonic fornetstatafter-puttana... I wonder if they designed it to yield these explicit references or whether it's just chance.
– Bakuriu
3 hours ago
1
For an 'all in one' linux command, check out fuser.fuser -k 8080/tcp 8080/udpshould kill anything listening on 8080.
– mbrig
3 hours ago
NB: The Windows command will also list all local processes that are connected to the webserver, at the instant that the command was run. The left address:port pair is the source address, the right address:port is the destination. Adding -t tcp will only list TCP connections, not UDP connections
– CSM
1 hour 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)
answered 20 hours ago
baelxbaelx
1,079615
Wow,-anois yet an other weird Italian mnemonic fornetstatafter-puttana... I wonder if they designed it to yield these explicit references or whether it's just chance.
– Bakuriu
3 hours ago
1
For an 'all in one' linux command, check out fuser.fuser -k 8080/tcp 8080/udpshould kill anything listening on 8080.
– mbrig
3 hours ago
NB: The Windows command will also list all local processes that are connected to the webserver, at the instant that the command was run. The left address:port pair is the source address, the right address:port is the destination. Adding -t tcp will only list TCP connections, not UDP connections
– CSM
1 hour 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)
answered 20 hours ago
baelxbaelx
1,079615
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)
answered 20 hours ago
baelxbaelx
1,079615
edited 20 hours ago
answered 20 hours ago
baelxbaelx
1,079615
answered 20 hours ago
baelxbaelx
1,079615
answered 20 hours ago
baelxbaelx
1,079615
1,079615
Wow,-anois yet an other weird Italian mnemonic fornetstatafter-puttana... I wonder if they designed it to yield these explicit references or whether it's just chance.
– Bakuriu
3 hours ago
1
For an 'all in one' linux command, check out fuser.fuser -k 8080/tcp 8080/udpshould kill anything listening on 8080.
– mbrig
3 hours ago
NB: The Windows command will also list all local processes that are connected to the webserver, at the instant that the command was run. The left address:port pair is the source address, the right address:port is the destination. Adding -t tcp will only list TCP connections, not UDP connections
– CSM
1 hour ago
add a comment |
Wow,-anois yet an other weird Italian mnemonic fornetstatafter-puttana... I wonder if they designed it to yield these explicit references or whether it's just chance.
– Bakuriu
3 hours ago
1
For an 'all in one' linux command, check out fuser.fuser -k 8080/tcp 8080/udpshould kill anything listening on 8080.
– mbrig
3 hours ago
NB: The Windows command will also list all local processes that are connected to the webserver, at the instant that the command was run. The left address:port pair is the source address, the right address:port is the destination. Adding -t tcp will only list TCP connections, not UDP connections
– CSM
1 hour ago
Wow,
-ano is yet an other weird Italian mnemonic for netstat after -puttana... I wonder if they designed it to yield these explicit references or whether it's just chance.– Bakuriu
3 hours ago
Wow,
-ano is yet an other weird Italian mnemonic for netstat after -puttana... I wonder if they designed it to yield these explicit references or whether it's just chance.– Bakuriu
3 hours ago
1
1
For an 'all in one' linux command, check out fuser.
fuser -k 8080/tcp 8080/udp should kill anything listening on 8080.– mbrig
3 hours ago
For an 'all in one' linux command, check out fuser.
fuser -k 8080/tcp 8080/udp should kill anything listening on 8080.– mbrig
3 hours ago
NB: The Windows command will also list all local processes that are connected to the webserver, at the instant that the command was run. The left address:port pair is the source address, the right address:port is the destination. Adding -t tcp will only list TCP connections, not UDP connections
– CSM
1 hour ago
NB: The Windows command will also list all local processes that are connected to the webserver, at the instant that the command was run. The left address:port pair is the source address, the right address:port is the destination. Adding -t tcp will only list TCP connections, not UDP connections
– CSM
1 hour ago
add a comment |
If you install ProcessExplorer from SystemInternals, then you can see the process tree.
In ProcessExplorer, click the target-sight button, and then click on the cmd prompt that you launched the webrowser from. ProcessExplorer will then jump to that cmd prompt in its list. If the process view is not already threaded by parent-child relation, then press Ctrl-T a few times until it is. You then should be able to see the webserver. Select it, and then right-click on it. Select "Kill Process Tree" to forcibly kill the webserver.
SystemInternals also has pskill. You can use pskill -t "MyWebServer" to kill all processes, and their children, than are called MyWebServer.
answered 1 hour ago
CSMCSM
54124
add a comment |
If you install ProcessExplorer from SystemInternals, then you can see the process tree.
In ProcessExplorer, click the target-sight button, and then click on the cmd prompt that you launched the webrowser from. ProcessExplorer will then jump to that cmd prompt in its list. If the process view is not already threaded by parent-child relation, then press Ctrl-T a few times until it is. You then should be able to see the webserver. Select it, and then right-click on it. Select "Kill Process Tree" to forcibly kill the webserver.
SystemInternals also has pskill. You can use pskill -t "MyWebServer" to kill all processes, and their children, than are called MyWebServer.
answered 1 hour ago
CSMCSM
54124
add a comment |
If you install ProcessExplorer from SystemInternals, then you can see the process tree.
In ProcessExplorer, click the target-sight button, and then click on the cmd prompt that you launched the webrowser from. ProcessExplorer will then jump to that cmd prompt in its list. If the process view is not already threaded by parent-child relation, then press Ctrl-T a few times until it is. You then should be able to see the webserver. Select it, and then right-click on it. Select "Kill Process Tree" to forcibly kill the webserver.
SystemInternals also has pskill. You can use pskill -t "MyWebServer" to kill all processes, and their children, than are called MyWebServer.
answered 1 hour ago
CSMCSM
54124
If you install ProcessExplorer from SystemInternals, then you can see the process tree.
In ProcessExplorer, click the target-sight button, and then click on the cmd prompt that you launched the webrowser from. ProcessExplorer will then jump to that cmd prompt in its list. If the process view is not already threaded by parent-child relation, then press Ctrl-T a few times until it is. You then should be able to see the webserver. Select it, and then right-click on it. Select "Kill Process Tree" to forcibly kill the webserver.
SystemInternals also has pskill. You can use pskill -t "MyWebServer" to kill all processes, and their children, than are called MyWebServer.
answered 1 hour ago
CSMCSM
54124
answered 1 hour ago
CSMCSM
54124
answered 1 hour ago
CSMCSM
54124
answered 1 hour ago
CSMCSM
54124
54124
add a comment |
add a comment |
Unless the process you're trying to kill is one that gets started upon booting the server, rebooting the computer in question would probably work. It's probably a last resort option due to losing everything else the computer's been doing that hasn't been saved, and the time it takes for the reboot to occur, but there's a reason why a lot of IT professionals start their troubleshooting process for user machines with "Have you tried turning the computer off and back on again?"
answered 9 hours ago
nick012000nick012000
95
New contributor
nick012000 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 |
Unless the process you're trying to kill is one that gets started upon booting the server, rebooting the computer in question would probably work. It's probably a last resort option due to losing everything else the computer's been doing that hasn't been saved, and the time it takes for the reboot to occur, but there's a reason why a lot of IT professionals start their troubleshooting process for user machines with "Have you tried turning the computer off and back on again?"
answered 9 hours ago
nick012000nick012000
95
New contributor
nick012000 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 |
Unless the process you're trying to kill is one that gets started upon booting the server, rebooting the computer in question would probably work. It's probably a last resort option due to losing everything else the computer's been doing that hasn't been saved, and the time it takes for the reboot to occur, but there's a reason why a lot of IT professionals start their troubleshooting process for user machines with "Have you tried turning the computer off and back on again?"
answered 9 hours ago
nick012000nick012000
95
New contributor
nick012000 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Unless the process you're trying to kill is one that gets started upon booting the server, rebooting the computer in question would probably work. It's probably a last resort option due to losing everything else the computer's been doing that hasn't been saved, and the time it takes for the reboot to occur, but there's a reason why a lot of IT professionals start their troubleshooting process for user machines with "Have you tried turning the computer off and back on again?"
answered 9 hours ago
nick012000nick012000
95
New contributor
nick012000 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 9 hours ago
nick012000nick012000
95
New contributor
nick012000 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 9 hours ago
nick012000nick012000
95
answered 9 hours ago
nick012000nick012000
95
95
New contributor
nick012000 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
nick012000 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
nick012000 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 |
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
