I've been having problems with LetsEncrypt not being presented on anything other than port 443. While trying to solve that problem, I've hit another on one SME 10 system. This one has been in service for quite a while - started life as an SME 7.2 system and has been migrated through several hardware changes as well as upgraded through different SME versions.
I was about to remove the LetsEncrypt setup completely, then reinstall it it see if I could solve the ongoing certificate problem when I discovered that the self-signed certificate what being renewed every 24 hours. No changes have been made to the templates in that area (I had a look at the Wiki item on changing the expiry date), and in each instance, the certificate was being renewed for a full year. The time stamp on the certificate was around 03:40 each night.
Since I wasn't sure whether this was connected to the problems I'm having with the LetsEncrypt certificates (see
https://forums.koozali.org/index.php/topic,54761.0.html), I removed LetsEncrypt and regenerated the self-signed certificate. After doing so, I found that the newly generated certificate was also being renewed every 24 hours. I then moved the
conf-mod_ssl script out of /etc/cron.daily, which stopped the constant renewal, at least until there was an upgrade and I did a
signal-event post-upgrade; signal-event reboot, which caused the certificate to be renewed again.
I've currently no idea what is causing this renewal, and I can't leave the daily check of the certificate disabled indefinately. I'm hoping somone may know what I need to look at to find the source of the problem.
4 Replies
1059 Views