** Chris Dennis via Hampshire [2017-02-13 12:39]:
> On 07/02/17 11:20, Paul Tansom via Hampshire wrote:
> >... I recently added my pop/imap mail server certificates to the process as
> >well (I'd forgotten they were still with StartSSL) and that was much easier
> >than expected - took about 10 min
On 07/02/17 11:20, Paul Tansom via Hampshire wrote:
... I recently added my pop/imap mail server certificates to the process as
well (I'd forgotten they were still with StartSSL) and that was much easier
than expected - took about 10 minutes including working out how to do it :)
Can you point m
** Samuel Penn via Hampshire [2017-02-08 15:36]:
> On Tuesday 07 Feb 2017 11:20:12 Paul Tansom via Hampshire wrote:
> > ** Imran Chaudhry via Hampshire [2017-02-07
> > 07:52]:
>
> > > +1 for letsencrypt.org - I recently switched to HTTPS for all my
> > > hosted server domains and was very happy
On Tuesday 07 Feb 2017 11:20:12 Paul Tansom via Hampshire wrote:
> ** Imran Chaudhry via Hampshire [2017-02-07
> 07:52]:
> > +1 for letsencrypt.org - I recently switched to HTTPS for all my
> > hosted server domains and was very happy to find a "letsencrypt"
> > package for Debian that automated
** Imran Chaudhry via Hampshire [2017-02-07
07:52]:
> On 1 February 2017 at 21:01, Thomas Kluyver via Hampshire
> wrote:
> > I'm not at all an expert on HTTPS, but if you're running a public web
> > server now, the standard advice is to use letsencrypt
> > (https://letsencrypt.org/ ) to create c
+1 for letsencrypt.org - I recently switched to HTTPS for all my
hosted server domains and was very happy to find a "letsencrypt"
package for Debian that automated the entire process. It even
auto-renews the cert for you.
On 1 February 2017 at 21:01, Thomas Kluyver via Hampshire
wrote:
> I'm not
I'm not at all an expert on HTTPS, but if you're running a public web
server now, the standard advice is to use letsencrypt
(https://letsencrypt.org/ ) to create certificates. They're free and you
can get them from an API, but unlike a self-signed certificate, it will
be trusted by all major browse
Along with the general move to using HTTPS I configured my webserver to
allow HTTPS connections.
However one of my users reported this error.
The certificate is not trusted because it is self-signed. The
certificate is only valid for bonzo.lan The certificate expired on 21
January 2017 at 13:
