According to our records, the software client you're using to get Let's Encrypt TLS/SSL certificates issued or renewed at least one HTTPS certificate in the past two weeks using the ACMEv1 protocol. Here are the details of one recent ACMEv1 request from each of your account(s):
Client IP address: xx.xx.xx.xx
User agent: CertbotACMEClient/0.40.1 (letsencrypt-auto; Debian GNU/Linux 9 (stretch)) Authenticator/webroot Installer/None (renew; flags: n hook) Py/2.7.13
Hostname(s): "domainname.at"
Request time: 2020-01-23 02:01:26 UTC
Beginning June 1, 2020, we will stop allowing new domains to validate using the ACMEv1 protocol. You should upgrade to an ACMEv2 compatible client before then, or certificate issuance will fail. For most people, simply upgrading to the latest version of your existing client will suffice. You can view the client list at: https://letsencrypt.org/docs/client-options/
If you're unsure how your certificate is managed, get in touch with the person who installed the certificate for you. If you don't know who to contact, please view the help section in our community forum at https://community.letsencrypt.org/c/help and use the search bar to check if there's an existing solution for your question. If there isn't, please create a new topic and fill out the help template.
ACMEv1 API deprecation details can be found in our community forum:
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1
As a reminder: In the future, Let's Encrypt will be performing multiple domain validation requests for each domain name when you issue a certificate.
While you're working on migrating to ACMEv2, please check that your system configuration will not block validation requests made by new Let's Encrypt IP addresses, or block multiple matching requests. Per our FAQ (https://letsencrypt.org/docs/faq/), we don't publish a list of IP addresses we use to validate, and this list may change at any time.
To receive more frequent updates, subscribe to our API Announcements:
https://community.letsencrypt.org/t/about-the-api-announcements-category
Thank you for joining us on our mission to create a more secure and privacy- respecting Web!
All the best,
Let's Encrypt
------------------------------
Here i was able to determine which certificates were using the old interface.
Just by changing the url from "server = *****://acme-v01.api.letsencrypt.org/directory" to "server = *****://acme-v02.api.letsencrypt.org/directory" and issuing a manual forced renew command like this: "/opt/certbot/certbot-auto renew --cert-name <certname> --force-renewal" i was able to switch.
This only works as the same account seems to be used both for v01 and v02.
had to exchange "https" by "*****" as i didn't have enough posts yet