AutoSNI LetsEncrypt Error: TypeError: Path must be a string. Received undefined about auto-sni HOT 11 CLOSED

Which version of auto-sni are you using? Which os?

from auto-sni.

512 MB Memory / 20 GB Disk / NYC3 - Debian 8.5 x64 ,
and install through
npm install auto-sni

, it should be the latest version because i just installed it.

from auto-sni.

And this error still exists after removing the debug option?
What is currently happening besides the error?

from auto-sni.

I had the same error and the browser was showing a big warning (because of self-signed certificate). I disabled debug mode, it worked, I switched it back and now, there is no error and I have the debug.

from auto-sni.

@shanoor thanks, I don't think this is actually a bug, more debug mode being descriptive.

@jefftham I think this should only be an "issue" for your initial run. Debug mode will print all errors, and the first time you run the error is that the certificate doesn't exist.

I am going to close this issue, but if this is not the case please let me know. In theory running your code again should not have any errors (and it should have been working properly the first time).

from auto-sni.

Thanks for you reply. Actually, the error is still occurred after i set the debug to false or delete the debug option. I really do not know why.

from auto-sni.

A question, it takes how long to generate the letsencrypt's cert and key? is it happened because i visit the website before the cert and key exist? Then, forced it to generate self-signed cert and key?

from auto-sni.

I'll spend some more time digging when I get a chance, likely tomorrow.

from auto-sni.

Thanks bro.

from auto-sni.

I'm having the same issue.

Adding the domainKeyPath key to the args object around line 50 in lib/load.js seems to fix it.
I just hardcoded a path and the error disappeared.

Of course, this is not a real fix but maybe helps you tracking it down.

from auto-sni.

@jefftham @sbugert sorry for the delay.

I have released [email protected] which locks down the letsencrypt version and stops this issue. Once I get some time, I will upgrade this library to use [email protected]. Help appreciated!

Let me know if this does not solve the issue for you guys.

from auto-sni.