As far as I understand, to create wildcard certificates, you need to put a key into a DNS record and this is a security issue because, once you have deposited it there, anyone on the internet can read it. This means you are only supposed to leave it there temporarily and managing that is not particularly easy. Some domain hosts such as Cloudflare have an API you can call to help with this function. It is a log term aim of Clearcenter to provide the possibility of using this sort of facility for all domains they host (including the poweredbyclear.com domain), but I don't see it on the near horizon yet.

Hi,

Is it possible to make wildcard certificate ?
Anyone some experience with this ?

I am not sure about the options and what happens if you are already running a web server (unless my instructions said to stop it first - I'll have to check).

My bad.

yum update app-lets-encrypt --enablerepo=clearos-contribs-testing

Nick Howitt wrote:

Thanks for the feedback. I'm sure I tested the instructions. Looks like I'll have to test again.

I am not sure about the options and what happens if you are already running a web server (unless my instructions said to stop it first - I'll have to check).

BTW there is a version of app-lets-encrypt patched to work with certbot-0.31 where the current version of the app fails when creating a new certificate (but not renewing one). You can install it with:

yum update app-lets-encrypt --enablerepo=clearos-updates-testing

Hi Nick,

There seems to be no update :

clearos-updates-testing                                                                 | 3.5 kB  00:00:00

(1/2): clearos-updates-testing/7/updateinfo                                             |   96 B  00:00:00

(2/2): clearos-updates-testing/7/primary_db                                             | 707 kB  00:00:00

No packages marked for update

Updated

Thanks for the feedback. I'm sure I tested the instructions. Looks like I'll have to test again.

I am not sure about the options and what happens if you are already running a web server (unless my instructions said to stop it first - I'll have to check).

BTW there is a version of app-lets-encrypt patched to work with certbot-0.31 where the current version of the app fails when creating a new certificate (but not renewing one). You can install it with:

yum update app-lets-encrypt --enablerepo=clearos-updates-testing

Nick Howitt wrote:

Hint. There is a documentation icon at the top of the webconfig screen .....

Hi Nick,

Thanks for the hint

Hint : update of the documentation .....

certbot certonly --cert-name -d domain1 -d domain2 -d domain3 ....

must be

certbot certonly --cert-name domain -d domain1 -d domain2 -d domain3 ....

certbot certonly --cert-name DOMAIN.nl -d DOMAIN.nl -d www.DOMAIN.nl

Saving debug log to /var/log/letsencrypt/letsencrypt.log



How would you like to authenticate with the ACME CA?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1: Apache Web Server plugin - Beta (apache)

2: Spin up a temporary webserver (standalone)

3: Place files in webroot directory (webroot)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Choose 2

Did you intend to make this change?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(U)pdate cert/(C)ancel: U

Choose U

Hint. There is a documentation icon at the top of the webconfig screen .....