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.

Sign up for GitHub

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

Jump to bottom

request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up () #14841

Closed
oyedejioyewole opened this issue Sep 8, 2022 · 8 comments
Closed

request to http://0.0.0.0:3000/__nuxt_vite_node__/manifest failed, reason: socket hang up () #14841

oyedejioyewole opened this issue Sep 8, 2022 · 8 comments
Labels
3.x pending triage

Comments

@oyedejioyewole
Copy link

Environment

  • 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)
@danielroe
Copy link
Member

Please see the note at the bottom of https://v3.nuxtjs.org/api/commands/dev#nuxi-dev.

nuxt/framework#7271

@danielroe danielroe closed this as not planned Won't fix, can't repro, duplicate, stale Sep 8, 2022
@oyedejioyewole
Copy link
Author

@danielroe I got this additional error

 ERROR  (node:25779) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)

and the same trace log errors

@danielroe Volta.net
Copy link
Member

That's not an error, just a warning from Node about the effect of setting the variable.

@oyedejioyewole
Copy link
Author

@danielroe but I still get the same trace log as

[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)

@danielroe Volta.net
Copy link
Member

Ah. You will need to be on edge channel to pull in the fix I linked above. See https://v3.nuxtjs.org/guide/going-further/edge-channel/.

@oyedejioyewole
Copy link
Author

oyedejioyewole commented Sep 8, 2022 •
edited

@danielroe but would this affect the modules I already have. I don't want my project to break. Isn't there another way

@danielroe Volta.net
Copy link
Member

You could also set vite.devBundler to legacy to keep previous behaviour until next rc.

@oyedejioyewole
Copy link
Author

oyedejioyewole commented Sep 8, 2022 •
edited

@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 😀

@danielroe danielroe added the 3.x label Jan 19, 2023
@danielroe danielroe transferred this issue from nuxt/framework Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.x pending triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danielroe @oyedejioyewole