Last night when I went to help someone sign up for sudo-humans, I saw that the
certificate had expired for
humans.sudoroom.org
I thought it had been made automatic by Alex a while ago, but i didn't really
understand what had been set up or know how it worked, so I had to figure it
out.
I don't know if this was the right way to fix it, but when I ran things like
certbot --standalone certificates -d
humans.sudoroom.org
it said that the certificate was already valid...but the page was saying it
was expired.
so I looked at /etc/apache2/sites-enabled/sudoroom.org.conf
and saw weird paths for SSLCertificate* that didn't correspond to what certbot
was using. So I changed it and then restarted apache2 and then it worked.
Since I don't know what I'm doing, maybe this will cause problems in the
future but I wanted to document what I did here.
# diff sudoroom.org.conf ~/sudoroom.org.conf.bak
23,26c23,25
< SSLCertificateFile /etc/letsencrypt/live/humans.sudoroom.org/cert.pem
< SSLCertificateKeyFile /etc/letsencrypt/live/humans.sudoroom.org/privkey.pem
< SSLCertificateChainFile /etc/letsencrypt/live/humans.sudoroom.org/fullchain.pem
---
SSLCertificateFile
/etc/letsencrypt/archive/hsr5/cert7.pem
SSLCertificateKeyFile /etc/letsencrypt/archive/hsr5/privkey7.pem
SSLCertificateChainFile /etc/letsencrypt/archive/hsr5/fullchain7.pem
yes of course we don't want to keep running
humans.sudoroom.org but until the
software gets updated to work on modern debian, we need to keep this working
so that sudoroom and CCL can continue to get payments from members.
Sierk and Ankeet have suggested they could update sudo-humans but I don't
think either of them have done anything yet. Also Charles Hughes may be
available but I don't know, anyway it's a separate topic.
-jake