OOTB install: localhost:3000 returns 404, Cannot GET /

[bebbi]

$ npm i -g create-react-app
$ create-react-app my-app
.. Success! ..
$ cd my-app
$ npm start
Starting the dev server ... Compiled successfully! .. running at http://localhost:3000/
Returned document in OSX/Chrome: Cannot GET /
console shows 404 error.

Does anyone have a quick idea for debugging this?
Btw: it's the same after ejecting. Using nvm0.31.3, node 6.3.0, npm 3.10.6

[gaearon]

This is weird and shouldn’t happen. Unfortunately it looks like some quirk specific to your Node setup because it doesn’t seem like other people are bumping into this.

If I was debugging this, I’d probably eject, put some logs into scripts/start.js and anything it calls (e.g. webpack-dev-server/lib/Server.js), as well as into html-webpack-plugin, and see why the server doesn’t serve index.html.

[bebbi]

I had a detached (node express) server process occupying port 3000 with nothing on the "/" route.
webpack-dev-server appears not to care about that.
When provoking a port conflict with another running server (python -m SimpleHTTPServer), webpack-dev-server even simply takes over. Maybe someone can teach webpack-dev-server some manners :)

[gaearon]

Maybe #101 will detect this.

[gaearon]

Can you try if the same problem is detected in the next alpha? Instructions to upgrade: #190

[bebbi]

works just fine for my test cases, including multiple sequential ports occupied.