XTension build 943 version 8.9.1

[Doug Kiekow]

Can’t this be worked around by installing the certificate on your router instead of on your server?

> On Sep 11, 2016, at 09·20 , James Sentman <james at sentman.com> wrote:
> 
> The problem is that setting up a signed certificate is just not easy. It’s not designed for our sort of situation. I’m experimenting with a $10 a year company now that I think will eventually work, but the process won’t be as automated as creating a self signed certificate. It will require steps like enabling the built in web server on MacOSX Server and putting a test file in there for the certificate company to hit and verify that you actually have access to the server dns name in question. There is also the problem about the IP address that it’s linked to not changing. Again certs are only really meant for regular servers with static IP addresses and I’m not sure what will happen when our IP addresses change.
>