Netlify Dev could not connect to locahost:3000

themetzmeier · February 10, 2022, 11:26pm

Hello,

While working on my development server, consistently a few minutes after having run netlify-dev I receive this error and am unable to call my functions until I kill node and restart netlify-dev, I am still able to access my website on port 3000 and make changes without any issues:

◈ Netlify Dev could not connect to localhost:3000.
◈ Please make sure your framework server is running on port 3000

This is really hampering my development and I can’t find a fix online. I am running Windows 10 21H1 and have netlify-lambda 2.0.15 and netlfiy-cli 9.2.0. My netlify.toml file is as follows:

[dev]
framework = “create-react-app”
functionsPort = 3001
[build]
functions = “lambda”
Command = “npm run prod”

hrishikesh · February 13, 2022, 4:34pm

Are you using Node 17 by any chance? if yes, this might help:

github.com/netlify/cli

Netlify Dev Server doesn't start on Node 17.x/18.x

opened 01:07PM - 10 Nov 21 UTC

closed 09:20AM - 19 Jul 22 UTC

Hrishikesh-K

medium priority type: bug area: command: dev

**Describe the bug** Similar to this: https://github.com/netlify/cli/issues/2…882#issue-939909811 Netlify Dev tries to start a server, it injects the environment variables, parses the configuration files and starts the local server of the framework, however it never starts the Netlify CLI's server. Till now, the behaviour has been observed with Vite and Create React App (but more frameworks could be affected). This has been observed on MacOS 12. Other Operating Systems have not been checked. This works with Node `14.17.5`, possibly with any other Node version than Node 17. **To Reproduce:** 1. Use Node 17 (17.0.1 at the time of writing). 1. Try running `netlify dev` in a project (possibly in a Vite or CRA project) 1. See that the dev server never starts. **Configuration** ```bash System: OS: macOS 12.0.1 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 891.31 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 17.0.1 - ~/.nvm/versions/node/v17.0.1/bin/node npm: 8.1.1 - ~/.nvm/versions/node/v17.0.1/bin/npm ``` **Expected behaviour** The Netlify Dev server should start. **CLI Output** Vite: ``` ◈ Netlify Dev ◈ ◈ Ignored general context env var: LANG (defined in process) ◈ Starting Netlify Dev with vite > dev > vite vite v2.4.1 dev server running at: > Local: http://localhost:3000/ > Network: use `--host` to expose ready in 217ms. ``` **Additional context** Marked `low-priority` as there's a workaround to use a different Node version.

themetzmeier · February 13, 2022, 5:35pm

No I am currently using Node 14.17.5

hrishikesh · February 13, 2022, 5:37pm

In that case, would it be possible to share the repo?

themetzmeier · February 13, 2022, 8:13pm

Not exactly but I may be able to share individual files that could help troubleshoot it, what might you need the package.json, package-lock.json, etc?

robations · February 14, 2022, 2:23pm

I’ve had a similar issue using gatsby v3. Netlify dev starts the gatsby dev server, which finishes, but netlify dev doesn’t recognise that it is ready to start proxying requests. See here:

github.com/netlify/cli

netlify dev could not connect to target server after long time out

opened 12:21PM - 30 Nov 21 UTC

closed 09:10AM - 30 Sep 22 UTC

robations

type: bug

**Describe the bug** The `netlify dev` command correctly starts the gatsby se…rver on port 8000, which is then running correctly. The most common scenario is there is a long pause (>10 minutes) then dev server says it can't connect to port 8000 and exits with an error code of 1. On one occasion it connected correctly (after the same long wait). At some point a few months ago this was working fine, unsure which dependency/environment/cli change has broken it. **To Reproduce** Steps to reproduce the behavior: 1. Run `git clone private git repo` 2. Navigate to the cloned repository 3. Run `netlify dev` 4. See that the CLI exits with an error Bear with me while I work on this. A discussion about this issue might help me or other people. Not at all easy to reproduce bugs with such complicated systems, e.g. do I need to set up another copy of WordPress for this reproduction? Please, tell me no... **Configuration** - If possible, please copy/paste below your `netlify.toml`. - Please enter the following command in a terminal and copy/paste its output: ```bash $npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli System: OS: macOS 11.6 Shell: 3.2.57 - /bin/bash Binaries: Node: 16.10.0 - ~/.asdf/installs/nodejs/16.10.0/bin/node Yarn: 1.22.15 - /usr/local/bin/yarn npm: 7.24.0 - ~/.asdf/installs/nodejs/16.10.0/bin/npm ``` **Expected behavior** Expecting dev server to connect to localhost:8000 shortly after gatsby has finished processing and has opened a port. **CLI Output** ``` You can now view my-project-name in the browser. ⠀ http://localhost:8000/ ⠀ View GraphiQL, an in-browser IDE, to explore your site's data and schema ⠀ http://localhost:8000/___graphql ⠀ Note that the development build is not optimized. To create a production build, use gatsby build ⠀ success Building development bundle - 97.505s ⠀ info gatsby-source-wordpress Watching for WordPress changes success Writing page-data.json files to public directory - 1.692s - 147/147 86.87/s success write out requires - 0.141s [ LONG WAIT AT THIS POINT ] ◈ Netlify Dev could not connect to localhost:8000. ◈ Please make sure your framework server is running on port 8000 Waiting for the debugger to disconnect... error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. Waiting for the debugger to disconnect... Process finished with exit code 1 ``` **Additional context** Is `netlify dev` waiting for some kind of signal/event from the child process to connect, or is it polling on a regular basis? NB the output log above is running with the debugger but it fails in the same way without the debugger.

Seemed like this was fixed by upgrade the netlify cli but I had the same problem today with the latest version.

Obviously it would be helpful to upgrade gatsby to rule out issues but we can’t risk upgrading to v4 right now.

hillary · February 17, 2022, 10:26pm

Hey there, @robations

Thanks for sharing that issue. Would it be possible to share your project repo as well as a link to your site? If not, can you share a reproduction?

hillary · February 17, 2022, 10:27pm

@themetzmeier sharing both your package.json and your package-lock.json would be great. Thanks in advance!

keneucker · March 9, 2022, 6:46am

I have a project where me, and other devs on this project, are experiencing this issue.

My repository: GitHub - KenEucker/biketag-vue: A vue app for the biketag game.

I am on Node (v16.13.2) and npm (8.1.2) with yarn (1.22.17) on a vite built web application.

I have found that it’s a “use it or lose it” sort of situation where 10 minutes or so of idle time (no requests made) the server will crash. It’s not always this way, as over time it eventually crashes immediately on a filechange. To be honest it’s hard to know the pattern other than the fact that it crashes with this error every single time without fail (eventually).

themetzmeier · March 9, 2022, 10:33pm

Interesting, I don’t think this is a dependency issue on the project itself, I started a new project with virtually zero dependencies and this was still occurring, so it must be my system. I tried disabling power-saving functionality related to network hardware but that did not yield any results either.

themetzmeier · March 9, 2022, 11:04pm

Here is the link to a repository having this issue, the package-lock.json and package.json are in the root directory:

RHEV · March 16, 2022, 5:10am

I have this same issue and have yet to look into it. I just accepted it as is, but now it’s enough of an inconvenience for me to dig into it. Repo is private unfortunately.

node v17.1.0
npm v8.1.0
netlify-cli v9.13.0

coelmay · March 16, 2022, 5:42am

Hey @RHEV

As mentioned earlier in this thread, there is an open issue for node v17. I suggest downgrading to v16 until it is resolved.

github.com/netlify/cli

Netlify Dev Server doesn't start on Node 17.x/18.x

opened 01:07PM - 10 Nov 21 UTC

closed 09:20AM - 19 Jul 22 UTC

Hrishikesh-K

medium priority type: bug area: command: dev

**Describe the bug** Similar to this: https://github.com/netlify/cli/issues/2…882#issue-939909811 Netlify Dev tries to start a server, it injects the environment variables, parses the configuration files and starts the local server of the framework, however it never starts the Netlify CLI's server. Till now, the behaviour has been observed with Vite and Create React App (but more frameworks could be affected). This has been observed on MacOS 12. Other Operating Systems have not been checked. This works with Node `14.17.5`, possibly with any other Node version than Node 17. **To Reproduce:** 1. Use Node 17 (17.0.1 at the time of writing). 1. Try running `netlify dev` in a project (possibly in a Vite or CRA project) 1. See that the dev server never starts. **Configuration** ```bash System: OS: macOS 12.0.1 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 891.31 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 17.0.1 - ~/.nvm/versions/node/v17.0.1/bin/node npm: 8.1.1 - ~/.nvm/versions/node/v17.0.1/bin/npm ``` **Expected behaviour** The Netlify Dev server should start. **CLI Output** Vite: ``` ◈ Netlify Dev ◈ ◈ Ignored general context env var: LANG (defined in process) ◈ Starting Netlify Dev with vite > dev > vite vite v2.4.1 dev server running at: > Local: http://localhost:3000/ > Network: use `--host` to expose ready in 217ms. ``` **Additional context** Marked `low-priority` as there's a workaround to use a different Node version.

RHEV · March 16, 2022, 5:42am

But I’ve worked so hard not to downgrade thusfar D:

coelmay · March 16, 2022, 5:44am

You might have to downgrade. v16 is an LTS release too (v17 is not) so will receive better and longer support as mentioned here.

RHEV · March 16, 2022, 5:49am

I’m aware of its’ long term support, but I need to build on 17 so sadly this solution won’t work for me. I’ll dig around when I have some time. Thank you for pointing me in the right direction!

bomzj · May 4, 2022, 11:26am

Having the same time out issue with stopping Netlify dev server when 10 or so minutes passed.
I’m using Netlify dev server for functions and Vite as web server. netlify-cli/10.1.0 win32-x64 node-v17.3.0
Error message from Netlify dev server:

Netlify Dev could not connect to localhost:3000.
Please make sure your framework server is running on port 3000

whereas my website is accessible on localhost:3000.

coelmay · May 4, 2022, 11:31am

The issue regarding Netlify CLI with v17 remains open on GitHub @bomzj (see links in previous posts.) At present the only option I am aware of is to downgrade to v16.

themetzmeier · May 4, 2022, 12:12pm

Any suggestions for the people not using Node v17 and still having this issue?

coelmay · May 4, 2022, 12:22pm

Are you referring to the repository you shared in a previous post @themetzmeier ?