[BUG] Wrong SSL certificate used. about zoraxy HOT 5 CLOSED

That self-sign certificate is the internal fallback certificate of your site. The Server Name (host name) field is the matching rule for that certificate. As you blurred out the domain name from the list, I cannot check it for you and I will assume you have read the instruction and fill it in correctly.

Then I will need more information to see what might cause this bug.

• Are you trying to access the domain via a sub-domain?
• Is your cert a SAN cert? (A cert that covers multiple host name or contains wildcards)
• What is your default site options? Will the issue be solve if you move the cert to the "fallback certificate" field? (you can get the certificate files by digging through the conf/certs/ folder)

from zoraxy.

Yes. Only sub Domains.
A.Domain.tld
b.Domain.tld
C.Domain.tld

Uhm... ist it a SAN cert? no clue. i used the ACME tool. Doesn't that automatically create a Wildcard Certificate?

Uploading the cert generated by Let's Encrypt found in /conf/certs folder did work. (though i mixed up .pem and .key first^^)
But it says only valid for domain.tld... so yeah, seems like that wasn't a Wildcard Certificate.

the original Problem is still the same.
You don't know which certificate is used for which Proxy Host.

from zoraxy.

Ok, it seems to be a wildcard certificate related issues.
Here let me introduce you the ACME module maintainer 😊
@yeungalan

In the mean time, can you try generate the cert using, let say one of the sub-domain, and connect through that sub-domain to see if that works?

from zoraxy.

Works fine.
use i.domain.tld, created a new Let's Encrypt Certificate via ACME, and properly used it on the correct domain.

So we end up with two issues:
A: Wildcard Certificates not working, as discussed here: #79

B: Not knowing which Certificate is used for which Proxy host... it just works magically correct, most of the time.

from zoraxy.

I just test again with a.domain.com,b.domain.com,c.domain.com and I can reproduce issue B.
After I generate the certificate via ACME and access a.domain.com, it served the site with default SSL certificate.
Let me figure out what might be the issue this weekend.

from zoraxy.