Open zhenweiwang1990 opened 8 years ago
Sorry for not responding sooner. This could easily be a bug in the current implementation. I'm seeing the following description in the ACME spec which matches the problem you're seeing
A certificate resource always represents the most recent certificate issued for the name/key binding expressed in the CSR. If the CA allows a certificate to be renewed, then it publishes renewed versions of the certificate through the same certificate URI.
https://letsencrypt.github.io/acme-spec/#certificate-issuance
I suppose RenewCertificate
might be a bad name for that function's current implementation.
when I call RenewCertificate , Letsencrypt will return a same cert or not. Which case is successful?
there is a comment here, in https://github.com/ericchiang/letsencrypt/blob/master/acme.go#L327 :
but there is also a comment here in https://github.com/xenolf/lego/blob/master/acme/client.go#L398 :
My problem is , when I try to renew, I always get the same certificate, but the cert's expire date never changed, so I think this is a result of failing renew?