On Fri, 28 Feb 2025 10:30:51 -0500, Frank Gingras <thumbs@xxxxxxxxxx> wrote:
>Moving to a modern mod_md approach might be better then, or alternatively,
>if you want to keep using the third party letsencrypt tools, asking your
>distro's support venues might work.
I don't want to move to a different method right now, just want to get the
migrated server running properly. Since it is on Ubuntu 24.04.1 I could test the
ubuntu maillist.
In any case I found some old notes from when I set it all up back in 2019 or so
and I ran a check command on the new server to see if it was OK with me having
migrated all of the related files below /etc to the new server (obfuscated the
domain name):
$ sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
Certificate Name: home.mydomain.com
Serial Number: 441f2...246ff1c8667e4a57b4c1cbdfab4
Key Type: RSA
Domains: home.mydomain.com svn.mydomain.com video.mydomain.com
Expiry Date: 2025-05-02 22:58:44+00:00 (VALID: 62 days)
Certificate Path: /etc/letsencrypt/live/home.mydomain.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/home.mydomain.com/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
So it seems to have migrated OK so far, I will check on the auto-renewal
functionality tomorrow.
--
Bo Berglund
Developer in Sweden
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|