GNU bug report logs -
#45082
Let's Encrypt certbot EOL for debbugs
Previous Next
Reported by: Bob Proulx <bob <at> proulx.com>
Date: Sun, 6 Dec 2020 21:09:02 UTC
Severity: normal
Done: Bob Proulx <bob <at> proulx.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 45082 in the body.
You can then email your comments to 45082 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
help-debbugs <at> gnu.org
:
bug#45082
; Package
debbugs.gnu.org
.
(Sun, 06 Dec 2020 21:09:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Bob Proulx <bob <at> proulx.com>
:
New bug report received and forwarded. Copy sent to
help-debbugs <at> gnu.org
.
(Sun, 06 Dec 2020 21:09:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Package: debbugs.gnu.org
Today in the cron mail came this message. We have reached the EOL end
of life for the EFF Certbot support on the debbugs host.
Date: Sun, 06 Dec 2020 06:02:06 -0500
From: Cron Daemon <root <at> debbugs.gnu.org>
To: root <at> debbugs.gnu.org
Subject: Cron <root <at> debbugs> /srv/letsencrypt/certbot-auto --quiet -n --apache renew
Your system is not supported by certbot-auto anymore.
Certbot will no longer receive updates.
Please visit https://certbot.eff.org/ to check for other alternatives.
Challenge failed for domain debbugs.gnu.org
Attempting to renew cert (debbugs.gnu.org) from /etc/letsencrypt/renewal/debbugs.gnu.org.conf pr
oduced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/debbugs.gnu.org/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
It's time to upgrade. I have switched my own systems to using the
"dehydrated" Let's Encrypt client. It's very portable. I have used
it on a variety of quite varied systems. This will allow us to keep
using debbugs without problems. We should get back to working on the
debbugs2p upgrade however.
The current https certificate expires 29-Dec-2020 and so I will plan
on having this switch accomplished prior to that certificate expiration.
Information forwarded
to
help-debbugs <at> gnu.org
:
bug#45082
; Package
debbugs.gnu.org
.
(Sun, 06 Dec 2020 23:16:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 45082 <at> debbugs.gnu.org (full text, mbox):
Thanks for looking at this. This was set up by sysadmin <at> gnu initially,
I have never dealt with it.
Reply sent
to
Bob Proulx <bob <at> proulx.com>
:
You have taken responsibility.
(Mon, 21 Dec 2020 20:35:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Bob Proulx <bob <at> proulx.com>
:
bug acknowledged by developer.
(Mon, 21 Dec 2020 20:35:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 45082-done <at> debbugs.gnu.org (full text, mbox):
Bob Proulx wrote:
> The current https certificate expires 29-Dec-2020 and so I will plan
> on having this switch accomplished prior to that certificate expiration.
I have updated the https certificate on debbugs. Now expiring +3
months from now. Since certbot is no longer supporting the older OS
on debbugs I switched it over to dehydrated which is more portable.
And simpler too.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 19 Jan 2021 12:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 148 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.