Hi, I deployed my first every https site last year on Digital Ocean using letsencypt. I was delighted to finally get a green ‘tick’ for a secure site and have diligently run the renew script every 3 months.
I have just configured my second server and, using updated instructions, got https working using certbot, which indicates it will auto-renew. Nice!
My question is, back on my first server, how do I migrate from using the ‘sudo letsencrypt renew --agree-tos’ command to asking certbot to automatically upgrade. Can I do a fresh Certbot deployment so it ‘takes over’ before my cert is expired? Do I need to wait until expiry? Or is there a migration approach I should consider while my cert is still valid?
Thanks in advance for any advice…
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: https://wealth-hack.com
I (normally) run this command: sudo letsencrypt renew --agree-tos
It produced this output:. It works, but manually requires me to do this every 3 months. I would like to automate using Certbot.
My web server is (include version): Apache/2.4.18 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu 16.04
My hosting provider, if applicable, is: Digital Ocean
I can login to a root shell on my machine (yes or no, or I don’t know): Yes.
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No, command line only.