A possibile bug in the site creations?

[wrtbitw]

Hi all,
I'm trying to implement Globaleaks (lastest version), but I'm running into an error configuring the Sites, especially an error with Let's Encrypt certificates.

The main domain is a third level domain (e.g. leaks.domain.tld) ​​and the configured Site is a fourth level domain (e.g. site.leaks.domain.tld).
The main domain (leaks.domain.tld) works correctly.

When I configure the network of the Site (site.leaks.domain.tld) with a Let's encrypt certificate, when I visit the site (site.leaks.domain.tld) ​​I'm running into a certificate error, specifically the fourth level domain site is exposed with the certificate of the main domain site (leaks.domain.ltd).

The only way for resolving the problem is by accessing againt into the site's network configuration, disabling the certificate and re-enabling it.

It seems to be a bug: the first let's encrypt certificate creation for a Site doesn't properly load the configuration so that the certificate must have disabled and re-enabled manually.

Has anyone run into the same problem or can you tell me if I'm doing something wrong?

Thanks a lot in advance.
Best regards.

[evilaliv3]

Hello @wrtbitw : Supid question but just to recheck all. Did you check that it is not a DNS configuration issue?

To get enabled by letsencrypt you should have a wildcard certificate for each level that you want to validate.
For example if you you want to validate 3 levels you need 2 wildcard entries like:

*.domain.tld
*.subdomain.domain.tld

i suspect you may have added only the first entry.