From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: patchwork.ipfire.org => Error: MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING
Date: Sun, 13 Oct 2019 01:25:04 +0200 [thread overview]
Message-ID: <59daa934-17fd-86fd-6533-dd0008ea4ca5@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
Hi,
today, suddenly patchwork.ipfire.org stopped working. Reloading the page
several times doesn't help. Firefox 69.0.3 keeps telling me:
***SNIP***
Secure Connection Failed
An error occurred during a connection to patchwork.ipfire.org. A
required TLS feature is missing. Error code:
MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING
The page you are trying to view cannot be shown because the
authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
***SNAP***
Setting "security.ssl.enable_ocsp_must_staple" in about:config to
"false" temporarily fixes this, but could it be that there is a problem
with the "Let's Encrypt" certificate!?
Can anyone confirm?
Best,
Matthias
P.S.: Possible solution (german!)
=>
https://www.kuketz-blog.de/nginx-aktivierung-von-ocsp-must-staple-ohne-timeout/
next reply other threads:[~2019-10-12 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 23:25 Matthias Fischer [this message]
2019-10-13 9:31 ` patchwork.ipfire.org does not supply OCSP information (was: Re: patchwork.ipfire.org => Error: MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING) peter.mueller
2019-10-13 11:17 ` patchwork.ipfire.org does not supply OCSP information Matthias Fischer
2019-10-13 16:01 ` Michael Tremer
2019-10-13 16:20 ` Matthias Fischer
2019-10-13 13:05 ` patchwork.ipfire.org => Error: MOZILLA_PKIX_ERROR_REQUIRED_TLS_FEATURE_MISSING Michael Tremer
2019-10-13 15:58 ` Matthias Fischer
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=59daa934-17fd-86fd-6533-dd0008ea4ca5@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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