Why doesn't Next.js recognize ssl certificate?
Answered
Asian black bear posted this in #help-forum
Asian black bearOP
I bought a certificate why doesn't Next.js doesn't recognize it? When I fetch through http works but with https error fetch message. Does anyone has faced the same issue?
Answered by Asian black bear
Yes we solved it. The solution is an another post. I wasn't setting right my ssl certificate.
9 Replies
now with the latest release does it work (as i see that they fixed something with certs
@riský now with the latest release does it work (as i see that they fixed something with certs
Asian black bearOP
I run the 13.5.3 but yet nothing.
Asian black bearOP
I will try run next@latest to see if it will be updated.
TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
cause: Error: unable to verify the first certificate
at TLSSocket.onConnectSecure (node:_tls_wrap:1600:34)
at TLSSocket.emit (node:events:517:28)
at TLSSocket._finishInit (node:_tls_wrap:1017:8)
at ssl.onhandshakedone (node:_tls_wrap:803:12)
at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}
}
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
cause: Error: unable to verify the first certificate
at TLSSocket.onConnectSecure (node:_tls_wrap:1600:34)
at TLSSocket.emit (node:events:517:28)
at TLSSocket._finishInit (node:_tls_wrap:1017:8)
at ssl.onhandshakedone (node:_tls_wrap:803:12)
at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}
}
Nothing
Pixiebob
@Asian black bear Did you manage to solve it?
Giant panda
@Pixiebob @Asian black bear did either of you solve it? I am able to fetch on http://localhost.com:3000 but not on https://localhost.com:3000 - using mkcert and local-ssl-proxy
Asian black bearOP
Yes we solved it. The solution is an another post. I wasn't setting right my ssl certificate.
Answer