From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org, Clark Fischer <cwfdevel@gmail.com>
Subject: Re: Expired Disarchive certificate
Date: Tue, 12 Nov 2024 08:33:50 +0000 [thread overview]
Message-ID: <D9B0BA4D-DF3B-4E82-BD9F-D2A88A008022@tobias.gr> (raw)
In-Reply-To: <87frnz2bb0.fsf@gmail.com>
Hi all, Clark,
Thanks for reporting this.
I was able to manually renew the certificate (below). I went ahead and upgraded to ECDSA.
I'm not myself a certbot user, so I'm not sure where to make the proper structural changes. Last I tried I think I edited some unused vestigial configuration.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
---
nckx@berlin ~$ sudo certbot certonly --manual -d disarchive.guix.gnu.org Password: Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - An RSA certificate named disarchive.guix.gnu.org already exists. Do you want to
update its key type to ECDSA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(U)pdate key type/(K)eep existing key type: u
Renewing an existing certificate for disarchive.guix.gnu.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Create a file containing just this data:
2hl4ITP-YUQ8GwjubFrHJm7JzFFINpVPx_il3BVlnWM.0L92hq7xCkluvkLfH4xT788boQdC7LjKBAnrnyd67Bw
And make it available on your web server at this URL:
http://disarchive.guix.gnu.org/.well-known/acme-challenge/2hl4ITP-YUQ8GwjubFrHJm7JzFFINpVPx_il3BVlnWM
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/disarchive.guix.gnu.org/fullchain.pem
Key is saved at: /etc/letsencrypt/live/disarchive.guix.gnu.org/privkey.pem
This certificate expires on 2025-02-10.
These files will be updated when the certificate renews.
NEXT STEPS:
- This certificate will not be renewed automatically. Autorenewal of --manual certificates requires the use of an authentication hook script (--manual-auth-hook) but one was not provided. To renew this certificate, repeat this same certbot command before the certificate's expiry date.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
* Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
* Donating to EFF: https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
nckx@berlin ~$ sudo pkill -HUP nginx
next prev parent reply other threads:[~2024-11-12 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 18:28 Expired Disarchive certificate Clark Fischer
2024-11-12 8:33 ` Tobias Geerinckx-Rice [this message]
2024-11-12 14:44 ` Clark Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9B0BA4D-DF3B-4E82-BD9F-D2A88A008022@tobias.gr \
--to=me@tobias.gr \
--cc=cwfdevel@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).