You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run you run yarn dev (which equates to npx nuxi dev --https --ssl-cert localhost.pem --ssl-key localhost-key.pem) you will get the error after the Vite client warmed up message.
Logs
[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)
The text was updated successfully, but these errors were encountered:
Environment
Darwin
v16.15.1
3.0.0-rc.9
0.5.0
yarn@1.22.19
vite
nitro
-
-
Reproduction
Run any nuxt v3 project with the
--https
option.Describe the bug
It appears part of the nuxt/vite code is trying to connect to http for a manifest file even though https has been selected.
Additional context
This is reproducible with the most simple code, eg https://github.com/chrisnoden/nuxt3-bug
Run you run
yarn dev
(which equates tonpx nuxi dev --https --ssl-cert localhost.pem --ssl-key localhost-key.pem
) you will get the error after the Vite client warmed up message.Logs
The text was updated successfully, but these errors were encountered: