<code> Let's Encrypt Certificates: The old and the new server must use the same Let's Encrypt client. If your old server uses Certbot, ensure that the new system uses Certbot, too, and not Acme.sh. If you install the new server using the ISPConfig auto-installer and your old server uses certbot, then use the command line switch --use-certbot in the auto-installer to install certbot instead of acme.sh on the new server. </code> Installed the new server following the perfect server debian 12, no autoinstaller, so acme.sh is installed. Do not remember what client is used. who to determine. and what if certbot is used. can I change this on the new server? Regards Rainer
First, you must check which LE client the old server is using. if the Let's Encrypt certificates are all in /etc/letsencrypt/live/.... folder, then it uses certbot. if they are in /root/acme.sh/.... folder, then it uses acme.sh. The new system should use the same LE client as mentioned in migration guide, otherwise yo LE certs will get migrated. The LE client should be chosen at install time, so install certbot and not acme. The auto-installer has a command-line option for this. In your situation, you can try to remove acme.sh and its certs completely and then install certbot instead and use ISPConfig update.sh function to create a new certificate during update. This might fix it, but I have not tested this. It would have been better if you had installed the new server with the correct LE client right away using the auto-installer.
<code> root@mike:~# find / -name acme.sh /root/.acme.sh/acme.sh </code> So I assume that is OK Regards Rainer
