Getting error Fetch failed, cause: unable to get local issuer certificate

Unanswered

୧ʕ•̀ᴥ•́ʔ୨ posted this in #help-forum

୧ʕ•̀ᴥ•́ʔ୨OP

2023-12-30T20:14:44.000Z

I am running next dev --experimental-https and can access the page locally via https://localhost, but the fetch still fails. If I put process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0" in next.config.js is works, but this isn't recommended from what I've read.

Any ideas what else to try?

14 Replies

Ray

2023-12-30T20:17:19.000Z

you gotta need NODE_TLS_REJECT_UNAUTHORIZED = 0 if you don't have a signed cert for the server

୧ʕ•̀ᴥ•́ʔ୨OP

2023-12-30T20:17:45.000Z

Isn't --experimental-https meant to resolve this?

It added a /certificates/ folder

I have localhost.pem and localhost-key.pem in it

Ray

2023-12-30T20:18:18.000Z

I think it just generate the cert for you

but it is not signed/trusted

୧ʕ•̀ᴥ•́ʔ୨OP

2023-12-30T20:22:18.000Z

Hmm, seems like a pain to get it to work

Is it bad to run NODE_TLS_REJECT_UNAUTHORIZED = "0" in development?

Ray

2023-12-30T20:23:59.000Z

oh i just tried, and it is an signed cert

what do you get error from?

୧ʕ•̀ᴥ•́ʔ୨OP

2023-12-30T20:25:29.000Z

It's an image, I have this in my next.config.js

remotePatterns: [
    {
        protocol: "https",
        hostname: "cdn.sanity.io",
        port: "",
        pathname: "/**",
    },
],

Ray

2023-12-30T20:26:30.000Z

remotePatterns: [
    {
        protocol: "https",
        hostname: "cdn.sanity.io"
    },
],

does this work?

୧ʕ•̀ᴥ•́ʔ୨OP

2023-12-30T20:28:26.000Z

No :/ It works fine if I set NODE_TLS_REJECT_UNAUTHORIZED = "0"

Ray

2023-12-30T20:28:52.000Z

well I think its fine to have NODE_TLS_REJECT_UNAUTHORIZED in dev mode