I found an error in /var/log/letsencrypt/letsencrypt.log Code: 2017-10-16 01:00:31,833:WARNING:letsencrypt.cli:Renewal configuration file /etc/letsencrypt/renewal/domain.tld.conf is broken. Skipping. 2017-10-16 01:00:31,835:DEBUG:letsencrypt.cli:Traceback was: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 900, in _reconstitute full_path, configuration.RenewerConfiguration(config)) File "/usr/lib/python2.7/dist-packages/letsencrypt/storage.py", line 200, in __init__ "file reference".format(self.configfile)) CertStorageError: renewal config file {} is missing a required file reference 2017-10-16 01:00:31,835:DEBUG:letsencrypt.cli:Exiting abnormally: Traceback (most recent call last): File "/usr/bin/letsencrypt", line 9, in <module> load_entry_point('letsencrypt==0.4.1', 'console_scripts', 'letsencrypt')() File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 1986, in main return config.func(config, plugins) File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 1034, in renew len(renew_failures), len(parse_failures))) Error: 0 renew failure(s), 1 parse failure(s) Code: root@panel:/var/log/letsencrypt# cat /etc/letsencrypt/renewal/domain.tld.conf root@panel:/var/log/letsencrypt# Should i be worried?
Looks like there won't be any renewals for that domain.tld in the future. I came across something about LE changing folder structure, didn't look too close into that but @till mentioned something about some fix/update ... @till ?
Latest certbot versions install themselves into /opt/eff.org/.... and ISPConfig recognizes that that since 3.1.7. But I'm not sure how LE handles it's own updates, I hope it does not leave it'sold version at the old place....
As long as ISPconfig looks in the new place, but why is it asking for a config file all of a sudden? Also, i have created another topic cuz i cant seem to put SSL (HTTPS) on for new websites...
It is not asking for a config file, it just tells you that a config file is syntactically wrong (or more precise, it is empty) and therefore it can not be parsed. You might have to remove the cert and config file for this cert and then let LE create a new one.