Hi there, I am using the LetsEncrypt Cert but I noticed that ISPConfig is not renewing as it should. I am using the ISPC ver 3.2.5. Ich searched a while for a solution, but I can find any. If I call /usr/local/ispconfig/server/server.sh, I get a "finished server.php" If I call /usr/local/ispconfig/server/lib/classes/cron.d/900-letsencrypt.inc.php I get a "PHP Fatal error: Uncaught Error: Class 'cronjob' not found in /usr/local/ispconfig/server/lib/classes/cron.d/900-letsencrypt.inc.php:31 I guess, the calling of 900-letsencrypt.inc.php is wrong to actualize the LetsEncrypt-Certificate manually. But how can I fix the problem, so the cert is actual again? Thanks für your help. Greetz Denise
Yes, you can't call the file like this manually, if you would want to call it, use cron_debug.php. But it is not likely that this will help you to solve your problem. Renewal is done by certbot or acme.sh, ISDPConfig just calls it once every night. Check letsencrypt.log or acme.sh log, depending on which LE client you use. The most likely reason for failing renewals are that you are using a certbot version that is too old or a domain/subdomain that is included in the SSL cert does not point to the server anymore in DNS. See also: https://www.howtoforge.com/community/threads/lets-encrypt-error-faq.74179/
Hi Till, thanks a lot for your help. I installed certbot by Code: apt install certbot python3-certbot-apache and by using Code: certbot --renew it functioned well. Sure, adding it to crontab would be a good idea....
It is there already, runs every night as @till said. If you refer to certbot site, most probably you will find that the newest way to install certbot is via using snap. Check it out there based on your server OS and its web server software.
Don't do that, your system will fail in this case with cert errors in future. ISPConfig takes care to run the command.