-
-
Notifications
You must be signed in to change notification settings - Fork 178
Nuxt 3 + Auth Module throws 500 Error when configured with https://localhost:3000 and Self Signed Certificate #484
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.
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
Comments
Same problem. The
nuxt-auth/src/runtime/utils/url.ts Line 7 in 45d7e34
Could be related to this: unjs-archive/is-https#8 https://github.com/unjs/is-https does not recognize |
After testing a bit, this problem is NOT an upstream problem (so I reopened the issue here) : 1°) This is NOT an upstream problem : Initially signaled as an upstream issue, this upstream was in the meantime closed by @danielroe : Please cf. this upstream issue page : nuxt/nuxt#22347 for reference You can convince yourself that 2°) With You can convince yourself that (only) the addition of the |
any plan to fix soon? or workarond? thanks |
Bump... 🙏 |
Thanks to this comment #374 (comment) |
Hello everyone! I assume this issue has been resolved. I will once again link the correct docs for Version 0.6 and above here: https://sidebase.io/nuxt-auth/v0.6/configuration/nuxt-config |
Hi,
Thanks for your fantastic work !
I am trying to set up an
https
devServer
with thisnuxt-auth
Auth Module + Nuxt 3, because someOAuth2
providers (likeInstagram
which I would like) require that you work withhttps://localhost:3000
, even on development mode.After a fresh install (Nuxt 3 + Auth Module + next-auth + the two pem files), I am receiving the following error when everything is set, when I try to
yarn dev
the project.I successfully created two pem files (with
mkcert
) with a self signed certificate (mkcert CA), and configured thenuxt.config.ts
lines as stated in the official nuxt 3 site as described in this page :SSL/TLS Certificates are working correctly
I am sure they do, because, when I add
ssr: false
on mynuxt.config.ts
file, I can correctly render the site withhttps://localhost:3000
Environment
Nuxi 3.6.3 15:36:46
Reproduction of the Error
On project directory, type
yarn dev
and click on> Local: https://localhost:3000/
Here is a repo to play with : https://github.com/rod2ik/https-auth-nuxt
Describe the bug
Both on the Terminal/IDE (I am using VSCode) and in my Browser (Firefox and Chrome) I receive the following error when I launch the site via
yarn dev
[nuxt] [request error] [unhandled] [500] fetch failed (https://localhost:3000/__nuxt_vite_node__/manifest)
What is weird is that it works fine (the page
https://localhost:3000
is correctly rendered) if I addssr: false
innuxt.config.ts
configurations (uncomnent line 4 ofnuxt.config.ts
file to test it)Browser Logs
Additional Context : h3 Logs
Additional Context : in the async
toNodeHandle()
function, on line 1359 of theh3
module, the h3 event is :The text was updated successfully, but these errors were encountered: