Hi Kyle,
Kyle Meyer writes:
> Anyway, based on how the expiration dates for various domains line up,
> it's usually okay if I don't act on that for a day or two, but in this
> case it bumped right against the list.orgmode.org expiration.
Great certificates expire alike :)
> Sorry about that
Bastien Guerry writes:
> Kyle, do you have any clue?
Yes. The SSL certs on my end are wired up to be automatically
refreshed. In order for them to be in effect, though, I need to
manually restart nginx. There's probably a better way to handle this,
but I just have a reminder.
Anyway, based
Ihor Radchenko writes:
> Side note: Regexp here is probably the reason why
> https://orgmode.org/list (without trailing slash) gives 404.
This should be fixed.
--
Bastien
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
Bastien Guerry writes:
> Ihor Radchenko 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",
Bastien Guerry writes:
> rewrite ^/list/(.*) https://list.orgmode.org/$1 permanent;
Side note: Regexp here is probably the reason why
https://orgmode.org/list (without trailing slash) gives 404.
Best,
Ihor
Ihor Radchenko 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.
Certificate for list.orgmode.org appears to be expired:
My browser is giving me ERR_CERT_DATE_INVALID
Best,
Ihor
