From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Firefox won't connect to git.ipfire.org
Date: Sat, 19 Jan 2019 18:26:05 +0100 [thread overview]
Message-ID: <45748de6-4af6-9b66-8c84-ad78f49e1d02@ipfire.org> (raw)
In-Reply-To: <c582cc34-8e6d-0a85-7c88-7c956b91b784@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
HI,
working again...
On 19.01.2019 18:21, Matthias Fischer wrote:
> Hi,
>
> On 19.01.2019 18:00, Bob Brewer wrote:
>> Started getting invalid certificate errors from Firefox when accessing any
>> https pages on git.ipfire.org. It was OK earlier and I can still access from
>> chrome(ium).
>>
>> Firefox Quantum 64.0
>>
>> "Your connection is not secure
>>
>> The owner of git.ipfire.org has configured their website improperly. To
>> protect your information from being stolen, Firefox has not connected to
>> this website.
>>
>> This site uses HTTP Strict Transport Security (HSTS) to specify that Firefox
>> may only connect to it securely. As a result, it is not possible to add an
>> exception for this certificate."
>>
>> Rob
>>
>
> In fact, the connection IS secure now ( ;-) ), I'm getting:
>
> ***SNIP***
> Gateway Timeout
>
> The gateway did not receive a timely response from the upstream server
> or application.
> ***SNAP***
>
> Best,
> Matthias
>
next prev parent reply other threads:[~2019-01-19 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 17:00 Bob Brewer
2019-01-19 17:16 ` Peter Müller
2019-01-19 17:21 ` Matthias Fischer
2019-01-19 17:26 ` Matthias Fischer [this message]
2019-01-19 17:55 ` Bob Brewer
2019-01-21 10:35 ` Michael Tremer
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=45748de6-4af6-9b66-8c84-ad78f49e1d02@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