Page 1 of 1
Let's Encrypt CLI Not Working - Error 15
Posted: Sat Aug 06, 2016 9:14 pm
by anthonyrossbach
I am trying to find a cause, but when I run the let's encrypt install using v-add-letsencrypt-domain I get a return with the message,
Code: Select all
Error: LetsEncrypt account registration 400
. When I dive into the error logs all I can see is
Code: Select all
2016-08-06 17:09:32 v-add-letsencrypt-domain '0etcnq48' '0etcnq48.n3.nodehost.ca' 'www.0etcnq48.n3.nodehost.ca,test.0etcnq48.n3.nodehost.ca' [Error 15]
When I use the user create I get
Code: Select all
2016-08-06 17:09:32 v-add-letsencrypt-user '0etcnq48' [Error 15]
Any ideas?
Re: Let's Encrypt CLI Not Working - Error 15
Posted: Sat Aug 06, 2016 9:56 pm
by imperio
Re: Let's Encrypt CLI Not Working - Error 15
Posted: Mon Aug 08, 2016 7:07 am
by SS88
Is there any LetsEncrypt logs? Even after
I still get this
Code: Select all
Error: LetsEncrypt account registration 400
but can't narrow down the error.
Re: Let's Encrypt CLI Not Working - Error 15
Posted: Mon Aug 08, 2016 11:15 pm
by RobertSP
Re: Let's Encrypt CLI Not Working - Error 15
Posted: Wed Aug 10, 2016 3:59 am
by anthonyrossbach
Now I get errors like this appearing when I try and generate some of the certs.
Code: Select all
2016-08-09 23:42:19 v-sign-letsencrypt-csr 'povgv7v4' 'digital.lammcs.com' '/tmp/tmp.N6Dw98CZ3N' [Error 8]
2016-08-09 23:42:19 v-add-letsencrypt-domain 'povgv7v4' 'digital.lammcs.com' 'www.digital.lammcs.com,povgv7v4.n3.nodehost.ca' [Error 8]
2016-08-09 23:49:59 v-sign-letsencrypt-csr 'povgv7v4' 'digital.lammcs.com' '/tmp/tmp.f7kZuacYEk' [Error 8]
2016-08-09 23:49:59 v-add-letsencrypt-domain 'povgv7v4' 'digital.lammcs.com' 'www.digital.lammcs.com,povgv7v4.n3.nodehost.ca' [Error 8]
2016-08-09 23:53:02 v-sign-letsencrypt-csr 'povgv7v4' 'digital.lammcs.com' '/tmp/tmp.nGPUXJOroc' [Error 8]
2016-08-09 23:53:02 v-add-letsencrypt-domain 'povgv7v4' 'digital.lammcs.com' 'www.digital.lammcs.com' [Error 8]
Re: Let's Encrypt CLI Not Working - Error 15
Posted: Wed Aug 10, 2016 4:04 am
by anthonyrossbach
It appears to be a permissions problem actually, as the same setup on a fresh account is fine.