From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: www.ipfire.org / forum.ipfire.org / blog.ipfire.org => TLS error
Date: Tue, 25 Dec 2018 10:18:31 +0100 [thread overview]
Message-ID: <0b5fe53b-2858-1fd7-4930-3f76fb99c845@ipfire.org> (raw)
In-Reply-To: <B15E2208-D8F2-4C9F-9A42-AEA3A8B958C3@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Hi,
On 25.12.2018 09:35, Michael Tremer wrote:
> Thanks for letting me know…
No problem...
> Haproxy lost its configuration file and therefore could not be reloaded to read the latest OCSP responses.
>
> Fixed that now. Let me know if there are any other problems.
>
> Merry Christmas!
Thanks for fixing - merry christmas to you too - and to all on the
list... ;-)
Best,
Matthias
> -Michael
>
>> On 25 Dec 2018, at 09:11, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> Hi,
>>
>> FYI, today the above three websites refused to load with the following
>> error message:
>>
>> "Secure Connection Failed
>>
>> An error occurred during a connection to forum.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."
>>
>> Can anyone confirm?
>>
>> Best,
>> Matthias
>
>
next prev parent reply other threads:[~2018-12-25 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 8:11 Matthias Fischer
2018-12-25 8:35 ` Michael Tremer
2018-12-25 9:18 ` Matthias Fischer [this message]
2018-12-25 19:44 ` Aw: " Bernhard Bitsch
2018-12-25 21:54 ` Michael Tremer
2018-12-25 22:23 ` Aw: " Bernhard Bitsch
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=0b5fe53b-2858-1fd7-4930-3f76fb99c845@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