From: Amin Bandali <amin@gnu.org>
To: Robert Klein <roklein@roklein.de>, Brent Goodrick <bgoodr@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: OK again, was: Re: Bug: git clone https://code.orgmode.org/bzg/org-mode.git fails with fatal: unable to access 'https://code.orgmode.org/bzg/org-mode.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none [9.1.7 (release_9.1.7-523-g594b2d @ /home/brentg/emacs_lisp_imported/org-mode/org-mode/lisp/)]
Date: Sat, 01 Sep 2018 11:59:30 -0400 [thread overview]
Message-ID: <875zzpqkd9.fsf@aminb.org> (raw)
In-Reply-To: <20180819185132.307c34d2@lt70.mpip-mainz.mpg.de>
Hi Robert,
> It seems the certificate for the web site expired. I managed to renew
> the certificate, so everything should work again as expected.
>
> The automatic renewal of certificates doesn't work at the moment, so we
> might encounter the issue again in a couple of months.
>
> I'll try to find a solution in the meantime.
Out of curiosity, what client is used for obtaining the LE certs?
Many of the clients offer a specific option for a "cron mode" or
could be used fairly painlessly in a cron job to periodically
check and renew the certs if necessary.
I'd be happy to try and help out with automating the renewal.
Best,
--
Amin Bandali | GNU webmaster | Grad student, UWaterloo
https://aminb.org | https://gnu.org | https://aminb.org/uw
GnuPG Key: CDDE 75F9 0353 8E71 813C DA27 D1FB A366 27D6 5876
prev parent reply other threads:[~2018-09-01 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 15:32 Bug: git clone https://code.orgmode.org/bzg/org-mode.git fails with fatal: unable to access 'https://code.orgmode.org/bzg/org-mode.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none [9.1.7 (release_9.1.7-523-g594b2d @ /home/brentg/emacs_lisp_imported/org-mode/org-mode/lisp/)] Brent Goodrick
2018-08-19 16:51 ` OK again, was: " Robert Klein
2018-08-25 22:37 ` Brent Goodrick
2018-09-01 15:59 ` Amin Bandali [this message]
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zzpqkd9.fsf@aminb.org \
--to=amin@gnu.org \
--cc=bgoodr@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=roklein@roklein.de \
/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/emacs/org-mode.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).