We have updated a ISPConfig-Server from Ubuntu 20.04 to 24.04 this weekend. This night, apache would not start anymore. It turned out, that there are some vhost-Files named <Domainname>.vhost-le-ssl.conf present with Paths to LE-Certs that no longer exist (e.g. /etc/letsencrypt/live/www.<Domainname>/privkey.pem). In other posts I read, that these files should not exist in a ISPConfig installation and result from a manual execution of certbot. I cant remember executing certbot manually, but it could have happened in the past. All these files are several years old (2018-2021) and most of these projects do not have LE enabled in ISPConfig anymore. Is it safe to just delete this vhosts from sites-available or what would be thy best way to clean this up. Any ideas, why this is causing problems just now? We also updated ISPConfig from 3.2 to 3.3 on the weekend.
These files are not from ISPConfig. You must have used certbot manually outside of ISPConfig, which created these files. I recommend to delete them, or better store them away as a backup until you are sure you don't need them anymore. ISPconfig 3.3 cleans up old unused certs.
Agreed. I do not think so, but opening respective domain websites settings and disabling the SSL + LE certs in there might work. Or you can delete the respective domain, if you are sure that you do not need them anymore. The reason is all domain's vhosts will be recreated if they are not deleted, and if their SSL + LE certs is ticked / enabled, the vhosts will add the LE SSL certs path in them. I think afterwards you should test via resync tool (tick website only). If thereafter apache restart fine, then only I think you are good to go.
