Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: eec.de
I ran this command: certbot cron job
It produced this output: none
My web server is (include version): Apache 2.4.18
The operating system my web server runs on is (include version): Ubuntu 16.04 LTS
My hosting provider, if applicable, is: myself
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Virtualmin
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): 0.23.0
At some stage my system started creating new config files whenever a new renewal was scheduled. My system obviously had some configuration issues (see Technical questions - config problems), but now I do not have any errors any longer, but only this “new config file issue”.
From what I can see, the new versions only differ by the version number, the rest is identical.
My current version of certbot is 0.23.0, the latest config files show 0.34.2, the latest version in the ppa is 0.31.0.
I refrained from activating the ppa in my software packages setup, as the version provided in the repository is still lower than the one in the config files. Moreover I fear that using the packages from the ppa may have side effects on my system.
Any idea, how I could keep certbot from creating new versions every month / two months?