@mouthpiec wrote:
Hi,
I got an email that certificates will expire soon, and when going through the logs of Let’sCert I got the below errors.This addon was installed when I had hassio running from the SDCard, but lately I shifted to SSD and I am using a docker, which makes me think that the paths inside the config file and not valid anymore.
Do you suggest to remove the addon and re-install it is the better solution?
> Saving debug log to /var/log/letsencrypt/letsencrypt.log > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Processing /data/letsencrypt/renewal/mydomain.com.conf > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > Traceback (most recent call last): > File "/usr/local/lib/python3.7/site-packages/certbot/renewal.py", line 64, in _reconstitute > renewal_candidate = storage.RenewableCert(full_path, config) > File "/usr/local/lib/python3.7/site-packages/certbot/storage.py", line 466, in __init__ > self._check_symlinks() > File "/usr/local/lib/python3.7/site-packages/certbot/storage.py", line 524, in _check_symlinks > "expected {0} to be a symlink".format(link)) > certbot.errors.CertStorageError: expected /usr/share/hassio/addons/data/core_letsencrypt/letsencrypt/live/mydomain.com/cert.pem to be a symlink > Renewal configuration file /data/letsencrypt/renewal/mydomain.com.conf is broken. Skipping. > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > No renewals were attempted. > > Additionally, the following renewal configurations were invalid: > /data/letsencrypt/renewal/mydomain.com.conf (parsefail) > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > 0 renew failure(s), 1 parse failure(s)
Posts: 1
Participants: 1