-1

I'm currently making a small react app using create-react-app . It worked smoothly for the last couple of weeks. But today things just stopped working. Everytime I run npm start I get Something already on port 3000 error.

So far I've tried npx kill-port, searching for running port but got nothing, ending node.exe process, and SET PORT. Nothing worked. Weird thing is that no matter what port I used it still got blocked. Any idea what caused this?

I am running on Node v12.18.0 and I used "start": "concurrently \" react-scripts start\" \"cd .. && node server\"

Here's the error:

[1] Node dev server: listening on port 5000
[0] Something is already running on port 3000.
[0] react-scripts start exited with code 0

Using SET PORT:

[1] Node dev server: listening on port 5000
[0] Something is already running on port 3156.
[0] SET PORT=3156 && react-scripts start exited with code 0
Atheralon
  • 21
  • 5
  • Please share the error logs – Verma Aman May 24 '21 at 10:47
  • @VermaAman sorry, here you go – Atheralon May 24 '21 at 12:07
  • Does this answer your question? [Node.js Port 3000 already in use but it actually isn't?](https://stackoverflow.com/questions/39322089/node-js-port-3000-already-in-use-but-it-actually-isnt) – jonrsharpe May 24 '21 at 12:59
  • @jonrsharpe Yeah I read that post, but it didn't help much. The port didn't appear in netstat so there's nothing I could do. I also tried Currports to monitor it but I got the same result. Nothing was running on that port before and during npm start. – Atheralon May 24 '21 at 13:13

0 Answers0