Display MoreThank you both for providing a solution.
I have found an even easier way to work around this issue. (Certificate creation works, Please revoke and reissue each certificate to make sure renewal is also using ACMEv02)
The latest Let's Encrypt i-MSCP plugin is using certbot 0.26.1 which is already capable of using ACMEv2. But it is not used by default.
You can change that by uncommenting line 796 in /var/www/imscp/gui/plugins/LetsEncrypt/backend/LetsEncrypt.pm so it looks like this:
Please keep in mind, that this files gets overwritten, when reinstalling or updating the Let's Encrypt Plugin.
I have followed these instructions. It does not work for me. Today I got an email from Letsyencrypt again that I use ACME V1 to renew the certificate. After the setting, the certificate was deleted as described above and created again. In the file /etc/letsencrypt/renewal/my-domain.de something changed after the new creation. The line with server = https://acme-v02.api.letsencrypt.org/directory and a few others have been added. Who can help me here. 01.06.2020 is the death line
- # renew_before_expiry = 30 days
- version = 0.10.2
- archive_dir = /etc/letsencrypt/archive/mydomain.de
- cert = /etc/letsencrypt/live/mydomain.de/cert.pem
- privkey = /etc/letsencrypt/live/mydomain.de/privkey.pem
- chain = /etc/letsencrypt/live/mydomain.de/chain.pem
- fullchain = /etc/letsencrypt/live/mydomain.de/fullchain.pem
- # Options used in the renewal process
- [renewalparams]
- account = XXXX My ACCOUNT XXXX
- server = https://acme-v02.api.letsencrypt.org/directory
- authenticator = webroot
- pref_challs = http-01,
- installer = None
- [[webroot_map]]
- mydomain.de = /var/www/imscp/gui/plugins/LetsEncrypt/acme