Hey, since 4 Days our Script dosent work correctly.
But we dont change anything for Certificates.
I get on each Domain the same issue:
Sign failed:
Log file is attached.
Script for install is here:
https://github.com/shoujii/NeXt-Server/blob/master/script/lets_encrypt.sh
Maybe anything is changed ? I hope anyone can help me.
Certs are in
/root/.acme.sh/DOMAIN.de_ecc
.cer
.conf
.csr
.key
And btw:
[Do 15. M盲r 19:41:39 CET 2018] url='https://acme-v01.api.letsencrypt.org/acme/challenge/RLnMOiy_cO5FZ6_cUUBbpva25U9bgeBnId6MXi2vWLo/3829833405'
[Do 15. M盲r 19:41:39 CET 2018] timeout=
Why acme use v1 and not v2?
Hey there, I've tested it with Certbot and it's working fine (retrieving Certs).
"Obtaining a new certificate
Performing the following challenges:
http-01 challenge for prs-script.de
Waiting for verification...
Cleaning up challenges"
Do we have to switch the the v2 Api to get it work in our Script?
We really want to use acme.sh, because we really like ECC Certs :P
@BoBBer446
@shoujii
For now, we only use v2 for wildcard certs. we will totally switch to v2 when v2 is stable enough in soon future.
I will check this issue soon.
Thanks.
Thanks in advance!
Hey,
Not sure if it's the same case, but I'm also getting "Sign failed" error. Log is attached.
@hertz1 @BoBBer446
please upgrade to the latest dev code, and try again with --debug 2
export BRANCH=dev
acme.sh --upgrade
Issued RSA + ECC Certs (havent' tested it yet if they're working now)
acme.sh.log
Most helpful comment
@BoBBer446
@shoujii
For now, we only use v2 for wildcard certs. we will totally switch to v2 when v2 is stable enough in soon future.
I will check this issue soon.
Thanks.