uduakabaci / Paisley

106 stars 8 forks source link

"self signed certificate in certificate chain" #2

Open thelegend09 opened 2 years ago

thelegend09 commented 2 years ago

Disclaimer: I'm not very knowledgeable with these things.

I've carefully followed all the steps in the Readme. But when I get to step #4, it doesn't work. I get this after I type npm start in the command line. (I'm using gmail to send mail, for the record).,

Error: self signed certificate in certificate chain
    at TLSSocket.onConnectSecure (_tls_wrap.js:1514:34)
    at TLSSocket.emit (events.js:400:28)
    at TLSSocket._finishInit (_tls_wrap.js:936:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:708:12) {
  code: 'ESOCKET',
  command: 'CONN'

Again, I've carefully followed all the steps. When it didn't work, I tried a few things.

In the subscribers-schema.yaml file, I tried with exactly the content from step 2. It didn't work. Then I changed the cron: '* * * * *' to cron: '1 * * * *'(to test if anything would be sent), but it didn't do anything. I changed it back.

In step 3, I created an .env file, but I didn't know what to name it. So I named it config.env, then process.env, and then I just called it .env. That’s when it seemed to worked the best, but still, it gave me what the code I copied above.


This is something brilliant that you’ve created, dev. I just wish I could figure out how to use it!! I'm almost certain it’s something dumb on my end. I just can't figure it out for the life of me.