Closed emulienfou closed 1 year ago
Thanks for reporting @emulienfou, will look into this when possible. My initial take is that it's weird that this diffs between node versions. It looks to me that this is a revocation from upstream (OpenSSL prob) from using the cert generated by selfsigned. We should probably change the cert generation params, it should be working on node 16.
Two questions which will speedup debugging: Which OS(linux, mac, windows) and version is triggering the issue? Have you validated that this works on the same machine with node 18 but not on 16?
Hi @TobiasMelen, I was running on Debian 11 with both latest versions of node J's 16 & 18. Switching from node 16 to 18 resolved the issue.
Hi @emulienfou I've increased encryption key size to 2048 and switched checksum algorithm to SHA256 which i hopes makes Debian happier to run the cert. Could you try installing this version, running it through node 16 on Debian to see if it's working better?
npm i next-dev-https@sha256
@TobiasMelen for reference purpose it was working fine on Node.js 16.20 but not on 16.15.
After install next-dev-https@sha256
on Nodejs 16.15, it works like a charm now!
Thanks for the fix
Thanks for reporting and testing, seems like selfsigned has quite lax certificate generation defaults, so it was good to bump them a bit. Change released in 2.0.1.
I may be wrong but it seems Nodejs 18 is the minimum required version to make this package work correctly!
With Nodejs 16 I got the next error message:
You should probably update your
package.json
to add the minimum version of the engine like:You could also specify that in the README file.