Hi all. I’m running the latest docker version from ownyourbits and am having issues getting my certificate from lets encrypt. When I run it I get the below output (modified to hide my domain)
[ letsencrypt ] Saving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: http-01 challenge for cloud.mydomain.com Using the webroot path /var/www/nextcloud for all unmatched domains. Waiting for verification... Cleaning up challenges Generating key (2048 bits): /etc/letsencrypt/keys/0002_key-certbot.pem Creating CSR: /etc/letsencrypt/csr/0002_csr-certbot.pem An unexpected error occurred: IOError: [Errno 2] No such file or directory: u'/etc/letsencrypt/live/cloud.mydomain.com-0001/cert.pem' Please see the logfiles in /var/log/letsencrypt for more details.
I actually tried this yesterday on an instance I had recovered and thought that perhaps something had gone wrong in the recovery, however when doing it today from a fresh install I got the same results. I should note that this isn’t a complete vaccume, I have also installed ddclient and pihole on this raspberry pi.
The 2nd to last line where it says No such file or directory: u’/etc/letsencrypt/… appears to be the major issue. I can tell the cert is being generated because I actually ran into the limit (apparently lets encrypt will only let you create 5 certs per subdomain per week, and I’m locked out for a bit now). I’ve done this before and it worked fine, so I’m wondering if there isn’t an bug in the latest docker image? That directory seems like garbage to me, and I’m guessing if whatever script called it dropped the u’ it would work just fine as etc/letsencrypt/live/ does exist in my docker container.
Am I on the right track here, and does anyone know if I can fix this or if the image has to be fixed?