3.0.0-rc.11 - $fetchRaw2 error - reason: connect EADDRNOTAVAIL :::3000 - Local
See original GitHub issueEnvironment
- Operating System:
Linux
- Ubuntu 20.04.5 LTS - Node Version:
v16.17.0
- Nuxt Version:
3.0.0-rc.11
- Nitro Version:
0.5.4
- Package Manager:
npm@8.15.0
- Builder:
vite
- User Config:
-
- Runtime Modules:
-
- Build Modules:
-
Reproduction
run…
npx nuxi init test-app
npm i
npm run dev
Describe the bug
After having an issue upgrading to the latest release candidate I get error…
500
request to http://[::]:32100/nuxt_vite_node/manifest failed, reason: connect EADDRNOTAVAIL :::32100 - Local (:::0) ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/shared/ohmyfetch.c2a48baf.mjs:132:20) at async ./.nuxt/dev/index.mjs:457:20 at async ./.nuxt/dev/index.mjs:526:64 at async ./.nuxt/dev/index.mjs:106:22 at async ./node_modules/h3/dist/index.mjs:592:19 at async Server.nodeHandler (./node_modules/h3/dist/index.mjs:538:7)
So I created a completely clean install but still get the same issue.
Additional context
No response
Logs
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:8
- Comments:12 (4 by maintainers)
Top Results From Across the Web
listen EADDRNOTAVAIL error in Node.js - Stack Overflow
It was fixed by changing the address my server was listening to. My config: app.set('port', process.env.PORT || 3000); ...
Read more >Node.js websocket error “Error: listen EADDRNOTAVAIL Error
Application work fine on localhost .but when its connect to server it getting error. I connect server through port 22.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Reproduction without Nuxt:
I think it might be best to default toForgot I already raised a PR that resolves this: https://github.com/unjs/listhen/pull/40.127.0.0.1
for vite-node as this will work even if no ipv4 port is open.A workaround for now is either to run
nuxt dev --host 0.0.0.0
(or127.0.0.1
if you are not running within a docker container) or to update your Dockerfile:Note: this will be resolved in the next release of
nuxi
that incorporates https://github.com/unjs/listhen/pull/40.Hi @danielroe 👋
In my case, I’m having this issue when I install the project and add SSL parameters to the script (using Node >= v18).
Complains about a
failed fetch
like the other comments https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V18.md#fetch-experimentalIf I downgrade to node version 16.18.0, it works.