I wiped a server, installed deb13 and did autoinstaller. I added --use-certbot in case I want to migrate from some older server. but now the cert for ns12.cdbsystems.com is NOT issued by letsencrypt - in fact: snip Subject Name Country DE State/Province None Locality None Organization None Organizational Unit IT Common Name ns12.cdbsystems.com Issuer Name Country DE State/Province None Locality None Organization None Organizational Unit IT Common Name ns12.cdbsystems.com Validity Not Before Wed, 06 May 2026 17:26:54 GMT Not After Sat, 03 May 2036 17:26:54 GMT snip is what the certificate presents. no lets encrypt, and firefox does not like it one bit! what happened to LE?
If you did not get an LE cert, then certbot was unable to issue one. Double check that ns12.cdbsystems.com really points to this new server in DNS and that the system is reaxhable on port 80 from the internet. You can reisue the cert by running: ispconfig_update.sh --force and choose to reconfigure services and to reissue the ssl cert when the updater asks. Besides that, check out the Let's Encrypt error FAQ post to get a checklist of what LE requires to issue a certificate, as a longtime user, you probably know that post.
I know it well! I'll track it down just asked in case certbot was NOT supported in deb13! I'm still playing with the migration problem Also any update to billing module after deb13 support? Or no need? Hope all is well with you and yours!
ISPConfig supports both LE clients on all supported OS versions. The Billing Module version 2.0.17 from August 2025, which is the most recent one, should be compatible with the PHP version used by Debian 13.
Agreed with @till that certbot is well supported for all supported OS in ISPConfig, and while I am not using Debian, I have no problem using certbot, even while using its dns-challenge method for the certs, so the right way to inspect is as advised above, troubleshoot with the steps mentioned in Let's Encrypt Error FAQ post.