tlsv1 unrecognized alert 112 about doc-buddy HOT 5 OPEN

I didn't add an nvm spec, but can you try using Node 16 because that's what I'm using.

from doc-buddy.

I've aded an .nvmrc and engines prop to the package.json so you should get a warning now if you're not using v16

from doc-buddy.

I am using node 16. Did a pull and have the nvmrc and am still seeing the same error.

$ node --version
v16.20.0

I will see if I can try to test on a real S3 bucket tomorrow. Any other debugging suggestions are welcome.

from doc-buddy.

I guess it's something to do with your cert, but I'm not sure. The error specifically says the server name is not present. Maybe we can change the s3 request to ignore ssl errors?

from doc-buddy.

I've never seen this error with any of my other services, so not sure what's different.

I'd be willing to give that a shot. Got a patch I can apply? It can at least help us narrow down where the problem is

from doc-buddy.