| From: | Mikael Kjellström <mikael(dot)kjellstrom(at)mksoft(dot)nu> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | buildfarm-members(at)postgresql(dot)org, buildfarm-admins(at)postgresql(dot)org |
| Subject: | Re: Moving to HTTPS |
| Date: | 2017-01-15 14:09:50 |
| Message-ID: | 20502717-9946-d876-2301-9f32ac5b48f6@mksoft.nu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-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:
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:
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-01-15 21:53:21 | Re: Moving to HTTPS |
| Previous Message | Andrew Dunstan | 2017-01-15 13:59:28 | Re: Moving to HTTPS |