public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: Firefox won't connect to git.ipfire.org
Date: Sat, 19 Jan 2019 18:16:08 +0100	[thread overview]
Message-ID: <245f4bae-5e1a-4f96-7d9f-cbec5156d56e@link38.eu> (raw)
In-Reply-To: <q1vl44$7oa$2@tuscan3.grantura.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

Hello Bob,

I cannot reproduce this here (tested using both Firefox and Tor
Browser, via different circuit paths).

Are there any further details available (expired certificates,
OCSP stapling information missing, ...)?

Thanks, and best regards,
Peter Müller


> 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
> 


-- 
Microsoft DNS service terminates abnormally when it recieves a response
to a DNS query that was never made.  Fix Information: Run your DNS
service on a different platform.
		-- bugtraq

  reply	other threads:[~2019-01-19 17:16 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 [this message]
2019-01-19 17:21 ` Matthias Fischer
2019-01-19 17:26   ` Matthias Fischer
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=245f4bae-5e1a-4f96-7d9f-cbec5156d56e@link38.eu \
    --to=peter.mueller@link38.eu \
    --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