From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>, Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] ERR_CERT_DATE_INVALID for https://list.orgmode.org/
Date: Sat, 18 Jun 2022 10:33:51 +0200 [thread overview]
Message-ID: <878rpu8j68.fsf@gnu.org> (raw)
In-Reply-To: <87h74iv3st.fsf@localhost> (Ihor Radchenko's message of "Sat, 18 Jun 2022 15:17:22 +0800")
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.
On the nginx config, there is:
server {
server_name orgmode.org;
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/xxx/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/xxx/privkey.pem;
include /etc/letsencrypt/options-ssl-nginx.conf;
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
rewrite ^/list/(.*) https://list.orgmode.org/$1 permanent;
}
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.
Kyle, do you have any clue?
--
Bastien
next prev parent reply other threads:[~2022-06-18 8:34 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 [this message]
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
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:
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=878rpu8j68.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
--cc=yantar92@gmail.com \
/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).