emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Bastien Guerry <bzg@gnu.org>
Cc: Kyle Meyer <kyle@kyleam.com>,  emacs-orgmode@gnu.org
Subject: Re: [BUG] ERR_CERT_DATE_INVALID for https://list.orgmode.org/
Date: Sat, 18 Jun 2022 17:46:33 +0800	[thread overview]
Message-ID: <8735g25mo6.fsf@localhost> (raw)
In-Reply-To: <878rpu8j68.fsf@gnu.org>

Bastien Guerry <bzg@gnu.org> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>> Certificate for list.orgmode.org appears to be expired:
>> My browser is giving me ERR_CERT_DATE_INVALID
> There is a CNAME record (handled by digitalocean.com) making the
> "list.orgmode.org" domain name an alias for "orgmode.yhetil.org",
> hosted by Kyle, which works fine.
> ...
> This is the configuration that used to work so far, I don't understand
> why it doesn't work anymore as I didn't change anything.  Certificates
> for orgmode.org and yhetil.org are OK.

I am not 100% sure if it is relevant, but
appears to say that list.orgmode.org should also have a valid

Looking at the certificate of list.orgmode.org, I see the following:

Common Name list.orgmode.org
 Not Before Sun, 20 Mar 2022 05:49:24 GMT
 Not After Sat, 18 Jun 2022 05:49:23 GMT
 SHA-1 7E:25:A8:B5:1A:DE:BF:67:F8:DD:22:C1:1B:E5:ED:7E:50:D0:D5:38

 Clearly, the certificate for list.orgmode.org expired today.


  parent reply	other threads:[~2022-06-18  9:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  7:17 [BUG] ERR_CERT_DATE_INVALID for https://list.orgmode.org/ Ihor Radchenko
2022-06-18  8:33 ` Bastien Guerry
2022-06-18  8:38   ` Ihor Radchenko
2022-06-18 11:41     ` Bastien
2022-06-18 12:50       ` Mastodon link type for capturing toots? Christian Moe
2022-06-20 12:56         ` Ihor Radchenko
2022-06-21 11:07           ` Christian Moe
2022-06-18  9:46   ` Ihor Radchenko [this message]
2022-06-18 10:25   ` [BUG] ERR_CERT_DATE_INVALID for https://list.orgmode.org/ Max Nikulin
2022-06-18 14:08   ` Kyle Meyer
2022-06-18 14:11     ` Bastien

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:

  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=8735g25mo6.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \


* 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


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).