public inbox for [email protected]  

help / color / mirror / Atom feed

From: Mikael Kjellström <[email protected]>
To: Andrew Dunstan <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: Moving to HTTPS
Date: Sun, 15 Jan 2017 15:09:50 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
List-Unsubscribe:  <mailto:[email protected]?body=unsub%20buildfarm-members>

On 2017-01-15 14:59, Andrew Dunstan wrote:

> The test should be thorough enough. If you want to try it for real and
> you're using the same that you built against, just change the URLs in
> your config file, i.e.:
>
>     sed -i -e
> s,http://www.pgbuildfarm.org/,https://buildfarm.postgresql.org/,
> your-config-file

I tried to surf to:

https://pgbuildfarm.org/

and I am getting that the certificate is invalid.  I see that you are 
using let's encrypt service for the SSL-certificate.  Just configure it 
to include all the DNS-names that you are using.   Currently the 
installed certificate is configured for the DNS-name:

buildfarm.postgresql.org

and with the SAN:

DNS Name: brentalia.postgresql.org
DNS Name: buildfarm.postgresql.org

I would suggest adding pgbuildfarm.org, www.pgbuildfarm.org etc also as 
SAN:s.

It's a pity that they don't support wildcard-certs though.

/Mikael


-- 
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members

view thread (15+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Moving to HTTPS
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox