good day guys,
i have a problem right now, my old server was centos 7 (already https using letsencrypt) and transferring /moving to our new server ubuntu 18.04.5 LTS (already https from our old centos 7).
Now i tried to renew it now cause its almost its expiry date.
where i will run the command
"cd letsencrypt"
"./letsencrypt-auto certonly --standalone"
but when i cd letsencrypt, i can't cd it, i notice it was missing from our new server ubuntu
note: in our centos 7 my letsencrypt folder was located at root (but can't be found anymore)
so i tried to install again the letsencrypt using "git clone https://github.com/letsencrypt/letsencrypt" now im using another location (/usr/local/bin ) not the same as centos(root)
now im in letsencrypt folder
i run "sudo certbot-auto renew" = i got "no renewals are attempted". it feels like im back to zero which letsencrypt reads my server as http not https, but my site is already https
when running command
certbot-auto certonly --standalone -d ourmail.com
its treating my zimbra as http
hope someone can help me, this is my first time seeing this problem after moving zimbra to a new server
No renewals found while renewing letsencrypt
-
- Elite member
- Posts: 1096
- Joined: Sat Sep 13, 2014 12:47 am
Re: No renewals found while renewing letsencrypt
Did you copy over the letsencrypt data store from the old server before trying to renew?
Usually it is a directory structure in /etc/letsencrypt
It has folders for the certificates (both live and archive), keys, csr, accounts and renewal (tells it how to renew the certificates), and renewal-hooks (if you have specified any)
Without having all of this copied over to the new server it is going to treat the new server as a completely new letsencrypt client.
Usually it is a directory structure in /etc/letsencrypt
It has folders for the certificates (both live and archive), keys, csr, accounts and renewal (tells it how to renew the certificates), and renewal-hooks (if you have specified any)
Without having all of this copied over to the new server it is going to treat the new server as a completely new letsencrypt client.