Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command: I didn’t run anything. The certificate is valid until November
It produced this output: It renews automatically EVERY day. No other domains on the same server do this. There are only two cronjobs - one hourly (keep-secured), and one weekly (remove-expired-tokens)
My web server is (include version): Plesk 18.0.29
The operating system my web server runs on is (include version): Unbuntu 18.04
My hosting provider, if applicable, is: Ionos
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Plesk 18.0.29
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
Issues like this are usually due to a malfunction in the ACME client. In this case, the Plesk Let’s Encrypt extension.
Sometimes it’s about failing to properly store the certificate (maybe the user’s disk is full), resulting in the next cronjob creating it from scratch. Sometimes it’s because there’s a mismatch between the domains it “wants” and the domains it’s actually issuing, so it’s never satisfied with the certificate it created last time. That one can crop up if wildcards are involved. Sometimes, as unlikely as it seems, there are multiple ACME clients competing over a domain,
If you have the latest version of the extension installed and it’s still happening, I would reach out to Plesk support and see whether they can investigate. There should be a sufficient log trail for them to figure it out.