From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] https with tcp80 in 2023?
Date: Thu, 11 May 2023 21:45:18 +0200 (GMT+02:00) [thread overview]
Message-ID: <09c5cc93-db84-4d77-9f39-9434aaea3074@sirjofri.de> (raw)
In-Reply-To: <98246906-4681-5ae7-c9f6-8ea20fd4d169@typed-hole.org>
11.05.2023 18:38:59 Julien Blanchard <julien@typed-hole.org>:
> Must be something with your cert, I have somewhat the same script and it still works as it used to.
I re-generated the cert (using the same account keys) and checked everything, it seems to work now. Whatever went wrong in the first place.
Thank you everyone. Best community 🙂
sirjofri
prev parent reply other threads:[~2023-05-11 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:35 sirjofri
2023-05-10 21:41 ` Yury Chumak
2023-05-10 22:11 ` unobe
2023-05-10 22:16 ` B. Atticus Grobe
2023-05-11 16:30 ` Julien Blanchard
2023-05-11 19:45 ` sirjofri [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09c5cc93-db84-4d77-9f39-9434aaea3074@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.org \
/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.
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 NNTP newsgroup(s).