request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
See original GitHub issueEnvironment
- Operating System:
Linux
- Node Version:
v16.16.0
- Nuxt Version:
3.0.0-rc.9
- Nitro Version:
0.5.1
- Package Manager:
yarn@1.22.19
- Builder:
vite
- User Config:
typescript
,modules
,app
,proxy
- Runtime Modules:
@nuxtjs/tailwindcss@5.3.2
,@pinia/nuxt@0.4.2
,@nuxtjs/proxy@2.1.0
,nuxt-svgo@1.0.1
- Build Modules:
-
Reproduction
I ran the following command
npx nuxt dev --https --ssl-cert ../cert/cert.pem --ssl-key ../cert/key.pem --open
Describe the bug
500 request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20) at async ./.nuxt/dev/index.mjs:457:20 at async ./.nuxt/dev/index.mjs:520: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)
Additional context
When I try running the server without --https
and it flags, the server loads and serves the page. This only happens for rc-9
as I upgraded from rc-8
Logs
Nuxi 3.0.0-rc.9 08:42:27
Nuxt 3.0.0-rc.9 with Nitro 0.5.1 08:42:27
08:42:29
> Local: https://localhost:3000/
> Network: https://192.168.43.111:3000/
ℹ Using default Tailwind CSS file from runtime/tailwind.css nuxt:tailwindcss 08:42:29
ℹ [HPM] Proxy created: /socket -> https://localhost:4000/socket 08:42:29
ℹ Tailwind Viewer: https://localhost:3000/_tailwind/ nuxt:tailwindcss 08:42:30
ℹ Vite client warmed up in 2286ms 08:42:33
ℹ Vite server warmed up in 361ms 08:42:33
✔ Nitro built in 615 ms nitro 08:42:34
[nuxt] [request error] [unhandled] [500] request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async ./.nuxt/dev/index.mjs:457:20
at async ./.nuxt/dev/index.mjs:520: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)
[nuxt] [request error] [unhandled] [500] request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async ./.nuxt/dev/index.mjs:457:20
at async ./.nuxt/dev/index.mjs:520:64
at async ./.nuxt/dev/index.mjs:106:22
at async ./node_modules/h3/dist/index.mjs:592:19
at async nodeHandler (./node_modules/h3/dist/index.mjs:538:7)
at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:354:29)
at async Server.nodeHandler (./node_modules/h3/dist/index.mjs:545:9)
[nuxt] [request error] [unhandled] [500] request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async ./.nuxt/dev/index.mjs:457:20
at async ./.nuxt/dev/index.mjs:520:64
at async ./.nuxt/dev/index.mjs:106:22
at async ./node_modules/h3/dist/index.mjs:592:19
at async nodeHandler (./node_modules/h3/dist/index.mjs:538:7)
at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:354:29)
at async Server.nodeHandler (./node_modules/h3/dist/index.mjs:545:9)
[nuxt] [request error] [unhandled] [500] request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async ./.nuxt/dev/index.mjs:457:20
at async ./.nuxt/dev/index.mjs:520: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)
[nuxt] [request error] [unhandled] [500] request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async ./.nuxt/dev/index.mjs:457:20
at async ./.nuxt/dev/index.mjs:520:64
at async ./.nuxt/dev/index.mjs:106:22
at async ./node_modules/h3/dist/index.mjs:592:19
at async nodeHandler (./node_modules/h3/dist/index.mjs:538:7)
at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:354:29)
at async Server.nodeHandler (./node_modules/h3/dist/index.mjs:545:9)
[nuxt] [request error] [unhandled] [500] request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up ()
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async ./.nuxt/dev/index.mjs:457:20
at async ./.nuxt/dev/index.mjs:520:64
at async ./.nuxt/dev/index.mjs:106:22
at async ./node_modules/h3/dist/index.mjs:592:19
at async nodeHandler (./node_modules/h3/dist/index.mjs:538:7)
at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:354:29)
at async Server.nodeHandler (./node_modules/h3/dist/index.mjs:545:9)
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Socket hang up on node js https request - Stack Overflow
i've searched through several tutorials and questions on stackoverflow and other sites but i can't still figure out why my script is producing ......
Read more >Error: socket hang up · Issue #2047 · request/request - GitHub
I tried to perform simple request: send form data. But when i use request module it always throw "socket hang up".
Read more >Socket hang up problems - Google Groups
It looks to me like the http.request() creation times out, and this is a bogus error message. However, I haven't been able to...
Read more >[Node] Socket hang up error with Node New Relic - Agents
Hi, recently we have experienced some socket hang up error with node new relic. Here is the timestamp when it happened.
Read more >Socket hang up while login using LinkedIn - Auth0 Community
Hi Sir, I am getting socket hang up error while login using LinkedIn, I looked for solution but didn't found the cause here...
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
You could also set
vite.devBundler
tolegacy
to keep previous behaviour until next rc.@danielroe currenty everything is still working which is great. I’m just going to stall updating soon to avoid breaking stuff. Thanks for your help 😀