emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] ERR_CERT_DATE_INVALID for https://list.orgmode.org/
Date: Sat, 18 Jun 2022 17:25:24 +0700	[thread overview]
Message-ID: <t8k96l$q88$1@ciao.gmane.io> (raw)
In-Reply-To: <878rpu8j68.fsf@gnu.org>

On 18/06/2022 15:33, Bastien Guerry wrote:
> Ihor Radchenko writes:
> The last line rewrites requests like
>    https://orgmode.org/list/875ynnojvf.fsf@localhost
> to
>    https://list.orgmode.org/875ynnojvf.fsf@localhost
> which is supposed to be handled by the CNAME alias.
> 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.

orgmode.yhetil.org, list.orgmode.org and yhetil.org sites have 
independent TLS certificates each one for 1 hostname.

Unless certificate for yhetil.org is renewed, it will have the same 
problem a week later.

  parent reply	other threads:[~2022-06-18 10:28 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   ` [BUG] ERR_CERT_DATE_INVALID for https://list.orgmode.org/ Ihor Radchenko
2022-06-18 10:25   ` Max Nikulin [this message]
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='t8k96l$q88$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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