How to kill a localhost:8080












4















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
















4















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














4












4








4








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

233




233




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


















4














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









4














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
















4














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














4












4








4







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

























answered 5 hours ago









baelxbaelx

919313




919313








  • 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





    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










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

Costa Masnaga

Image
.mw-parser-output .avviso .mbox-text-div>div,.mw-parser-output .avviso .mbox-text-full-div>div{font-size:90%}.mw-parser-output .avviso .mbox-image div{width:52px}.mw-parser-output .avviso .mbox-text-full-div .hide-when-compact{display:block} Questa voce o sezione sull'argomento Lombardia non cita le fonti necessarie o quelle presenti sono insufficienti . Puoi migliorare questa voce aggiungendo citazioni da fonti attendibili secondo le linee guida sull'uso delle fonti. Segui i suggerimenti del progetto di riferimento. Costa Masnaga comune Localizzazione Stato   Italia Regione Lombardia Provincia Lecco Amministrazione Sindaco Sabina Panzeri (Al centro il cittadino) dall'08/06/2009 Territorio Coordinate 45°46′N 9°17′E  /  45.766667°N 9.283333°E 45.766667; 9.283333  ( Costa Masnaga ) Coordinate: 45°46′N 9°17′E  /  45.766667°N 9.283333°E 45.766667; 9.283333  ( Costa Masnaga ) Altitudine 318 m s.l.m...
Read more

Fotorealismo

Image
Guerrino Boatto, Venice's St. Barnaba Church and canal Il fotorealismo è un genere di pittura basato sull'uso di una o più fotografie dalle quali l'artista prende le informazioni necessarie da utilizzare poi nel processo della creazione dell'opera, in genere ad olio o ad acrilico, al fine di avere un aspetto finale il più simile possibile alla fotografia. Indice 1 Storia 2 Lista dei fotorealisti 3 Note 4 Voci correlate 5 Altri progetti Storia | Il fotorealismo è un movimento che nasce negli Stati Uniti d'America alla fine degli anni sessanta [1] sulla scia della Pop Art [2] [3] [4] , e insieme condividono il carattere reazionario verso la travolgente ascesa dei media, che alla metà del ventesimo secolo si trasforma in un fenomeno di massa talmente imponente da minacciare il valore dell'immagine nell'arte. [5] [6] Ne consegue così che, colto il gesto d'inizio che fu della Pop Art, i fotorealisti aprono ad un ...
Read more

Sidney Franklin

Image
Questa voce sull'argomento registi statunitensi è solo un abbozzo . Contribuisci a migliorarla secondo le convenzioni di Wikipedia. Sidney Franklin, foto di Carl Van Vechten Oscar alla memoria Irving G. Thalberg 1943 Sidney Franklin , all'anagrafe Sidney Arnold Franklin , (San Francisco, 21 marzo 1893 – Santa Monica, 18 maggio 1972), è stato un regista, produttore cinematografico e attore statunitense. Il 20 giugno 1963, si sposò con l'attrice australiana Enid Bennett. Il matrimonio durò fino alla morte dell'attrice, il 14 maggio 1969 [1] Indice 1 Filmografia 1.1 Regista 1.2 Aiuto regia (parziale) 1.3 Produttore 1.4 Attore (parziale) 2 Note 3 Altri progetti 4 Collegamenti esterni Filmografia | Regista | The Baby , co-regia Chester M. Franklin (1915) The Rivals , co-regia Chester M. Franklin (1915) Little Dick's First Case , co-regia Chester M. Franklin (1915) Her Filmland Hero , co-...
Read more