Extension reissues certificates after switching to manually uploaded certificate

[oliver-graetz]

This is an update to my problem in issue #81 .

The original problem was: We are experiecing rate limit problems for a domain because it seems that Plesk doesn't see that there is a valid certificate. At least it's trying to renew the certificate every hour. Approximately once a day I get a mail from Plesk with the message "too many certificates already issued for exact set of domains".

After some months of hoping that some update fot the Lets Encrypt extension would fixe the problem, I finally decided to stop using Lets Encrypt for some time and then start using it again later. So I did this:

• I downloaded all certificate components.
• Then I set the domain to not use the Lets Encrypt certificate anymore.
• This allowed me to delete the certificate. From this point I considered the Lets Encrypt as not active for this domain.
• Then I manually created a certificate entry using all of the downloaded components except the CSR.

This was done hoping that I could reconfigure Lets Encrpt later. But here's what happened:

Just two days later, I get the error mail again and sure, looking in Plesk, the extension was still active, had issued a new certificate, activated that and deactivated the manually issued certificate. And the problems described in issue #81 were back on track.

How on earth do I get the Lets Encrypt extension to stop going berserk for that particular domain?

[oliver-graetz]

This is using Lets Encrypt version 2.6.1-398.

[grimurd]

I have the same problem with multiple domains on my server (the original problem).