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 browsers.
Thomas
On Wed, Feb 1, 2017, at 08:58 PM, Stephen Davies via Hampshire wrote:
> 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:51. The current time is 1 February 2017 at 20:49.
> Error code: SEC_ERROR_UNKNOWN_ISSUER
>
>
> Some expert guidance on how I can resolve this would be most welcome.
> The system was built just over a year ago hence the certificate expiry.
> As it said, the cert currently in use is self signed but as yet I've not
> explicitly done anything regarding certs in the webserver.
>
> Thanks,
> Stephen Davies.
>
>
>
>
> --
> Please post to: Hampshire@???
> Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
> LUG URL: http://www.hantslug.org.uk
> --------------------------------------------------------------
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
