I recently moved my site to a new hosting company. in the process I went from ubuntu 14.04 to ubuntu 16.04. with the 14.04 system, I installed certbot using wget per the certbot website instructions and used the webroot method to obtain my certs since nginx plugin support is still experimental. on the 16.04 system, I installed let’s encrypt from the repositories as directed by certbot. my /etc/letsencrypt directory was copied from the old server to the new one.
when I ran the letsencrypt renew --dry-run command, it gave me the following error::
Processing /etc/letsencrypt/renewal/mysite.com.conf 2016-09-26 21:05:47,997:WARNING:letsencrypt.cli:Attempting to renew cert from /etc/letsencrypt/renewal/mysite.com.conf produced an unexpected error: 'server'. Skipping. ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/mysite.com/fullchain.pem (failure) ** DRY RUN: simulating 'letsencrypt renew' close to cert expiry **(The test certificates above have not been saved.) 1 renew failure(s), 0 parse failure(s)
I’m not really sure what ‘server’ means as far as an error. is it an issue that I went from certbot to letsencrypt?
something I also noticed is that on my other ubuntu server in my house (14.04), I use the following command to renew my certs:
whereas with ubuntu 16.04, the certbot site tells me to simply use:
will that suffice? will it know what I ran to initially grabbed the certs because I haven’t ran it on the new server yet? I’m assuming it might be stores in the /etc/letsencrypt folder somewhere…
any help is appreciated!