Vjylku

I am on the US no-fly list. What can I do in order to be allowed on flights which go through US airspace?

Which aircraft had such a luxurious-looking navigator's station?

What are these green text/line displays shown during the livestream of Crew Dragon's approach to dock with the ISS?

Is there any relevance to Thor getting his hair cut other than comedic value?

How to count words in a line

How to approximate rolls for potions of healing using only d6's?

Understanding Kramnik's play in game 1 of Candidates 2018

Where is the fallacy here?

What do the pedals on grand pianos do?

What is this waxed root vegetable?

Did Amazon pay $0 in taxes last year?

Pure Functions: Does "No Side Effects" Imply "Always Same Output, Given Same Input"?

Second-rate spelling

How to speed up a process

Linear regression when Y is bounded and discrete

Make me a metasequence

Replacement ford fiesta radiator has extra hose

Is there a low-level alternative to Animate Objects?

Is there a ternary operator in math

Can you use a beast's innate abilities while polymorphed?

Difference between 'stomach' and 'uterus'

Multiplication via squaring and addition

Why does the 31P{1H} NMR spectrum of cis-[Mo(CO)2(dppe)2] show two signals?

Logistics of a hovering watercraft in a fantasy setting

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

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

edited 4 hours ago

JakeGould

31.6k1097139

asked 5 hours ago

SamSam

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.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just double checking but is this issue happening on a Windows machine?
  
  – JakeGould
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @JakeGould Yes it is.
  
  – Sam
  4 hours ago
  

  
  
  
  

add a comment | 

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

edited 4 hours ago

JakeGould

31.6k1097139

asked 5 hours ago

SamSam

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.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Just double checking but is this issue happening on a Windows machine?
  
  – JakeGould
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @JakeGould Yes it is.
  
  – Sam
  4 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

share|improve this question

edited 4 hours ago

JakeGould

31.6k1097139

asked 5 hours ago

SamSam

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.

share|improve this question

edited 4 hours ago

JakeGould

31.6k1097139

asked 5 hours ago

SamSam

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.

share|improve this question

edited 4 hours ago

JakeGould

31.6k1097139

asked 5 hours ago

SamSam

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.

edited 4 hours ago

JakeGould

31.6k1097139

edited 4 hours ago

JakeGould

31.6k1097139

asked 5 hours ago

SamSam

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.

asked 5 hours ago

SamSam

183

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

edited 4 hours ago

answered 5 hours ago

baelxbaelx

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
  

  
  
  
  

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.

draft saved

draft discarded

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

Name

Email

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

Name

Email

Required, but never shown

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

edited 4 hours ago

answered 5 hours ago

baelxbaelx

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
  

  
  
  
  

add a comment | 

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

edited 4 hours ago

answered 5 hours ago

baelxbaelx

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
  

  
  
  
  

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)

share|improve this answer

edited 4 hours ago

answered 5 hours ago

baelxbaelx

909313

sudo lsof -iTCP:8080 -sTCP:LISTEN

COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME

yarn    12017 user   12u  IPv6 1876683      0t0  TCP *:8080 (LISTEN)

kill 12017(whatever the PID is)

kill -9 12017

netstat -ano | findstr :8080 (the port number)

taskkill /F /PID 12017(or whatever the process ID is)

share|improve this answer

edited 4 hours ago

answered 5 hours ago

baelxbaelx

909313

answered 5 hours ago

baelxbaelx

909313

answered 5 hours ago

baelxbaelx

909313