Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't npm start in a new app #121

Closed
josechavezm opened this issue Jul 23, 2016 · 5 comments · May be fixed by rangle/create-react-app#15
Closed

Can't npm start in a new app #121

josechavezm opened this issue Jul 23, 2016 · 5 comments · May be fixed by rangle/create-react-app#15

Comments

@josechavezm
Copy link

HI everybody,

I'm doing npm start in a just created app and it won't work.
it throws the following:

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE 127.0.0.1:3000
    at Object.exports._errnoException (util.js:1012:11)
    at exports._exceptionWithHostPort (util.js:1035:20)
    at Server._listen2 (net.js:1252:14)
    at listen (net.js:1288:10)
    at net.js:1398:9
    at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:65:16)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:84:10)

Also, I have
npm 3.10.3
node 6.3.1
in a ubuntu machine.

@keyz
Copy link
Contributor

keyz commented Jul 23, 2016

Thanks for reporting. Do you have another npm start instance running? It probably means you have another app that uses the 3000 port so this one fails. #117, #101, and #100 all address this issue.

@josechavezm
Copy link
Author

Oh that's the problem. I feel really dumb, I'm sorry.
Thank you.

@keyz
Copy link
Contributor

keyz commented Jul 23, 2016

No, our error message should be better :)

@keyz keyz closed this as completed Jul 23, 2016
@gaearon
Copy link
Contributor

gaearon commented Jul 27, 2016

New alpha should offer to listen on another port. Please give it a try! Here's how: #190

@kuznets
Copy link

kuznets commented Sep 23, 2017

Hi, I get same error at the first app start.
I check 3000 port with netstat -natp it is clean.
I check npm process with ps aux | grep npm it is not started.
I try "PORT=3005 npm start" and get same error.

@lock lock bot locked and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants