Upgrading the OS underlying Let'sEncrypt/certbot... How?

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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domains are: www.theturners.org, www.systypes.org, and www.systypes.com. (I will likely be giving up the systypes.com domain in June.)

I ran this command: apt update

It produced this output: Several 404 errors about the OS no longer being supported. Software is running on a Raspberry Pi 4 running the "Stretch" version. Yes... pretty old hence the question about upgrading the OS. I'm looking to upgrade the hardware to a Raspberry Pi 5 and the OS on the rPi 4 is no longer supported. It is my understanding that simply swapping the SD card is not an option.

I suspect I'll need to go through the certbot installation all over again. If so, what does that process entail? I assume I'll be starting over from scratch but how will that impact existing domains' certificates?

My web server is (include version): The system running certbot is using Nginx 1.10.3 as a proxy server for the main Apache 2.4.59 (running on a different system).

The operating system my web server runs on is (include version): Raspbian "Stretch" (again, needs an upgrade)

My hosting provider, if applicable, is: N/A

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): N/A

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 2.10.0

Certbot has been trouble-free since installation so I haven't needed any sort of support until now.

TIA for any assistance.

Hi @rnturner, and welcome to the LE community forum :slight_smile:

It shouldn't impact you much: Your HTTPS sites will be unavailable until you get all new cert.
But obtaining them should be simple and straightforward.
You only need to ensure to either:

  • remove all references to any certs not available [to get nginx to start]
    OR
  • include a copy of the entire /etc/letsencrypt/ folder [with symlinks] to the new Pi 5 proxy system

It's simple.
See: Certbot (eff.org)
[and choose nginx and whatever OS the Pi 5 will be running for complete installation instructions]
[I say it that way because (I take nothing for granted) I'm running Ubuntu 23.10 on my Pi 5]

5 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.