What I suspect happened here is:
- The server at
2a01:4f8:150:1229::2
has the same account under/etc/letsencrypt/accounts
as your other server as well as a certificate for the exact same domains. - Something is configured on the server at
2a01:4f8:150:1229::2
to automatically runcertbot renew
. This may be your own scripts, however, I think it is (also) probably the systemd timer included in the Certbot .deb package. - The server at
2a01:4f8:150:1229::2
made use of authz reuse to issue a certificate for those domains despite not being able to prove control of that domain itself. - The server at
2a01:4f8:150:1229::2
used the ACMEv1 endpoint due to the problem described above.
To fix the issue, if the server is not in use, I’d either:
- Use
sudo certbot delete
to delete the certificate so the default systemd timer in the Certbot package won’t try to renew it anymore. - Uninstall the
certbot
package and optionally delete/etc/letsencrypt
to remove all account and certificate information from the server.