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











  • @JakeGould Yes it is.

    – Sam
    4 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
    4 hours ago











  • @JakeGould Yes it is.

    – Sam
    4 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 4 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
    4 hours ago











  • @JakeGould Yes it is.

    – Sam
    4 hours ago



















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

    – JakeGould
    4 hours ago











  • @JakeGould Yes it is.

    – Sam
    4 hours ago

















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

– JakeGould
4 hours ago





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

– JakeGould
4 hours ago













@JakeGould Yes it is.

– Sam
4 hours ago





@JakeGould Yes it is.

– Sam
4 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
    4 hours ago











  • @JakeGould took my words right out of my own mouth. Would this work on windows?

    – Sam
    4 hours ago






  • 1





    Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating

    – baelx
    4 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
    4 hours ago











  • @JakeGould took my words right out of my own mouth. Would this work on windows?

    – Sam
    4 hours ago






  • 1





    Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating

    – baelx
    4 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
    4 hours ago











  • @JakeGould took my words right out of my own mouth. Would this work on windows?

    – Sam
    4 hours ago






  • 1





    Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating

    – baelx
    4 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
    4 hours ago











  • @JakeGould took my words right out of my own mouth. Would this work on windows?

    – Sam
    4 hours ago






  • 1





    Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating

    – baelx
    4 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
    4 hours ago











  • @JakeGould took my words right out of my own mouth. Would this work on windows?

    – Sam
    4 hours ago






  • 1





    Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating

    – baelx
    4 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
4 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
4 hours ago













@JakeGould took my words right out of my own mouth. Would this work on windows?

– Sam
4 hours ago





@JakeGould took my words right out of my own mouth. Would this work on windows?

– Sam
4 hours ago




1




1





Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating

– baelx
4 hours ago





Thanks for pointing that out! I missed that. You can use a similar set of tools. Updating

– baelx
4 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

Reichsarbeitsdienst

Image
Hausflagge des RAD mit Symbol Staatssekretär Konstantin Hierl schreitet auf dem Tempelhofer Feld die Front des RAD ab. Maifeier Berlin, 1. Mai 1934 RAD beim Straßenbau, 1936 RAD-Parade: „Der große Aufmarsch der 38.000 Arbeits­dienst­männer vor dem Führer auf dem Zeppelin­feld“, „Reichs­partei­tag der Arbeit“. Männer des RAD mit ge­schulter­tem Spaten vor Hitler im Auto, 6.–13. Sep. 1937 Reichsparteitag Nürnberg, Arbeits­dienst-Zeltlager mit Arbeitsmaiden, August 1939 Paramilitärischer Aufmarsch des Ar­beits­dienstes, ca. 1940 Vormaliges RAD-Lager (4/224), Ober­mill­statt, um 1940 erbaut als Quartier für junge, zum Arbeits­dienst eingezogene Frau­en, auch Bund Deutscher Mädel (BDM), die bei den Ober­mill­stätter Bauern ein­gesetzt waren, 1950 Der Reichsarbeitsdienst ( RAD ) war eine Organisation im nationalsozialistischen Deutschen Reich. Das Gesetz für den Reichsarbeitsdienst wurde am 26. Juni 1935 erlassen. § 1 (2) lautete: „Alle jungen Deutschen beider
Read more

Statuo de Libereco

Image
Koordinatoj: 40°41′21″N 74°02′40″W   /   40.68917°N , 74.04444°U  / 40.68917; -74.04444  ( Statuo de Libereco ) Statuo de Libereco angle: Statue of Liberty statuo Statuo de Libereco de antaŭe Oficiala nomo: Liberty Enlightening the World Lando  Usono Ŝtato Novjorkio Regiono Novjorko Insulo Insulo de Libereco Situo Statuo de Libereco  - koordinatoj 40°41′21″N 74°02′40″W   /   40.68917°N , 74.04444°U  / 40.68917; -74.04444  ( Statuo de Libereco ) Alteco de statuo 46 m  - alteco kun soklo 93 m Pezo 205 000 kg (451 948 lb) Materialoj bronzo, ŝtalo Proponinto Gustave Eiffel  - skulptisto Frédéric Auguste Bartholdi  - proponinto de soklo Richard Morris Hunt  - kapo laŭ modelo de Isabella Eugenie Boyer Transdonita 4-an de julio 1886 Por publiko alirebla por publiko Horzono OT (UTC-5)  - somera tempo OT (UTC-4) Loko
Read more

Tanganjiko

Image
Lago Tanganjiko Situo centra Afriko Ĉefaj fontoj Kalambo, Lufuko, Malagarasi kaj Ruzizi Ĉefaj elfluoj Lukugo Setlejoj Bujumbura, Kalemie Datenoj Koordinatoj 6°  S , 30°  O -6.3827777777778 29.615 782 Koordinatoj: 6°  S , 30°  O DEC Supermara alteco 782 m Surfaca areo 32 893 km² f5 Maksimuma longo 673 km f6 Maksimuma larĝo 72 km f7 Akva volumeno 18.900 km³ dep1 f8 Maksimuma profundo 1470 m f10 Averaĝa profundo 570 m f11 v   •   d   •   r Mapo de la lago Tanganjiko estas lago en orienta Afriko, inter Burundo, Kongo Kinŝasa, Tanzanio kaj Zambio. Ĝi apartenas al la Granda Rifto kaj estas unu el la Afrikaj Grandaj Lagoj. Tanzanio (46%) kaj DRK (40%) havas la majoritaton de la lago. Ĝi havas longon de 673 km, areon de ĉ. 32.900 km² kaj maksimuman profundon taksatan je 1470 metroj; pro tiu ĉi granda profundo ankaŭ ĝia volumeno estas sufiĉe granda, 18.900 km³. Oni konsi
Read more