• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Input Lets encrypt renewal failure limitation

TomBoB

Regular Pleskian
Server operating system version
almalinux 8 latest
Plesk version and microupdate number
plesk 18.0.45 (latest)
One subscription, one main domain with two aliases.
When an alias has a problem renewing, it blocks all else also from renewing.
It would be great if the problem domain is excluded from the subsequent renewal attempt so that the rest still becomes/stays secured.

Client case:
His setup one subscription, two aliases were migrated to another server. Plesk dns via DO extension adjusted automatically.
It was overlooked that one alias was registered via godaddy and pointed to old name servers.
So the DNS changes in Plesk were not public for that domain name as it still used the old name servers pointing at the old server.

On renewal time the alias could not be renewed [at the time the old server was partialy decommissioned and lets encrypt renewal complained about a missing ipv6]

In essence, not being able to renew that one alias stopped the main domain as well as the other alias its cert to be renewed.

Only came to light after the client received a notification about cert expiration and we started investigating.

It would be great if a little flexability for cases like this could be added to the renewal process. :)
 
Back
Top