How to kill a localhost:8080












3















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







share|improve this question









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.





















  • Just double checking but is this issue happening on a Windows machine?

    – JakeGould
    5 hours ago











  • @JakeGould Yes it is.

    – Sam
    5 hours ago
















3















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







share|improve this question









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.





















  • Just double checking but is this issue happening on a Windows machine?

    – JakeGould
    5 hours ago











  • @JakeGould Yes it is.

    – Sam
    5 hours ago














3












3








3








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







share|improve this question









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. 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






share|improve this question









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.











share|improve this question









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.









share|improve this question




share|improve this question








edited 5 hours ago









JakeGould

31.6k1097139




31.6k1097139






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 5 hours ago









SamSam

183




183




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.













  • 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











  • @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










1 Answer
1






active

oldest

votes


















3














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)





share|improve this answer





















  • 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











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.










draft saved

draft discarded


















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









3














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)





share|improve this answer





















  • 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
















3














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)





share|improve this answer





















  • 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














3












3








3







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)





share|improve this answer















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)






share|improve this answer














share|improve this answer



share|improve this answer








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














  • 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










Sam is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

404 Error Contact Form 7 ajax form submitting

Image
0 The contact form does not work, and affects loading after one try. The chrome console shows the error message: POST http://example.com/wp-json/contact-form-7/v1/contact-forms/50/feedback 404 (Not Found) send @ jquery.js?ver=1.12.4:4 ajax @ jquery.js?ver=1.12.4:4 wpcf7.submit @ scripts.js?ver=5.0.3:346 (anonymous) @ scripts.js?ver=5.0.3:53 dispatch @ jquery.js?ver=1.12.4:3 r.handle @ jquery.js?ver=1.12.4:3 How to solve this issue? thanks in advance javascript wordpress contact-form-7 share | improve this question edited Jul 17 '18 at 5:39 Kiran Shahi 4,745 3 16 43 ...
Read more

How to know if a Active Directory user can login interactively

Image
1 I would like to know if and how is it possible to know if a AD user can login interactively (on a server) in a domain. I need to know if I can find it out using a LDAP search. Thanks. windows active-directory login user-permissions user-profile share | improve this question edited 1 hour ago yagmoth555 ♦ 11.6k 3 17 42 asked 1 hour ago Luigi Luigi 6 1 New contributor ...
Read more

Refactoring coordinates for Minecraft Pi buildings written in Python

Image
0 $begingroup$ I'm fairly new to coding and I wrote this script in Python for a house with a roof in Minecraft Pi. I've found different ways to write the coordinates to make the code base shorter, but I'm wondering if it is possible for me to refactor it any further so I don't have to list each coordinate line by line. import mcpi.minecraft as minecraft import mcpi.block as block mc = minecraft.Minecraft.create() p = mc.player.getTilePos() mc.setBlocks(p.x+1, p.y, p.z+1, #Main structure starting coordinates (DO NOT ALTER) p.x+19, p.y+4, p.z+6, #Structure size/coordinates (Alters cube size) block.STONE_BRICK) mc.setBlocks(p.x+2, p.y+1, p.z+2, #Hollowing out main structure interior p.x+18, p.y+3, p.z+5, block.AIR) mc.setBlocks(p.x, p.y...
Read more