The Raspberry Pi has now arrived at its third generation. Yet I’m still running an old Pi model B+ (single core, 512 MB of ram) as my owncloud server, and it works just fine! The Pi is running Raspbian wheezy, which (being Debian) will be supported until 31st May 2018, so I don’t really have urgency to upgrade it. The only annoyance is that I’m using a self-signed SSL certificate. Now that Let’s Encrypt is a thing, I’ve been trying to get a proper certificate, but turns out that my Raspbian is too old for that.
The (officially recommended)
certbot-auto script fails when attempting to install
wheezy-backports, a Debian repository that was never officially ported to Raspbian.
So the script will attempt to download these ARMv7-compiled packages from debian, while the Pi B+ model has an ARMv6 cpu.
Solution: rebuild those packages
certbot-auto script should have created the
/etc/apt/sources.list.d/wheezy-backports.list file with the following content:
apt-get install packages from this repo, but you can download their sources and rebuild them on the Pi itself!
This is as simple as running the following commands (credits to this gist):
First of all, install the build-dependencies. This will pull a lots of packages (including latex stuff), but fortunately they all come from the Raspbian repos:
Then get the required source code from the wheezy-backport repo:
Now you can start the build. This will take a while…
At this point you should have the following packages:
Now just install all of them (even though technically you only need two):
certbot-auto --os-packages-only. If everything went as expected, you should see this message:
OS packages installed.
This means that you are ready to use
certbot-auto to get or renew your SSL certificates!