Let's Encrypt on subdomain (configured as domain) not working

[Bitpalast]

Situation:

maindomain.xx has a fully functional Let's Encrypt certificate.

The customer has also subdomain.maindomain.xx and has set that up by adding a domain (not adding a subdomain), so that it should behave as if it was a maindomain.

He has a certificate from Let's Encrypt installed. We have checked the certificate listed in the nginx.conf and httpd.conf files, decrypted it and are seeing that is is the correct certificate for the domain name. Both server configuration files (nginx.conf and httpd.conf) show the correct certificate.

Nginx and Apache were both restarted after configuration changes.

Issue:

When connecting to subdomain.maindomain.xx the browser does not receive the subdomain.maindomain.xx certificate, but the hostname.yy certificate of the physical machine that Plesk is running on. The subdomain does neither deliver the maindomain.xx, nor the subdomain.maindomain.xx certificate despite the correct configuration files.

Why is that and how can it be solved?

 

[Alvin_Allen]

The SSL needs to be installed on the subdomain. You should be able to install the certificate for the subdomain from within Plesk or from the command line (see: http://docs.plesk.com/en-US/12.5/cl...utilities/certificate-ssl-certificates.39009/ ); in addition, Plesk has a "Let's Encrypt" extension: https://ext.plesk.com/packages/f6847e61-33a7-4104-8dc9-d26a0183a8dd-letsencrypt which allows you to manage the Let's Encrypt SSL's from within Plesk--for domains and subdomains.

I've installed Let's Encrypt SSL's on all of my domains (and subdomains) using the Let's Encrypt Plesk extension without issue.

 

[Bitpalast]

Can you please send me a PN with a link to one of your subdomains where a Let's Encrypt certificate is running?

 

[Bitpalast]

I would also like to add, that the issue only occurs when both, the main domain and the subdomain, want to use the Let's Encrypt certificate generated by the extension. If the main domain uses a different SSL certificate, the subdomain can use a Let's encrypt cert, but if the main domain has a Let's Encrypt cert, the subdomain cannot also have one.

 

[Bitpalast]

Meanwhile two other Plesk users have demonstrated that they are using different Let's Encrypt certs on main domain and sub domain. So there seems to be a way. Yet unsolved why Plesk delivers the hosts's certificate despite the correct certificates set in main domain and sub domain. Where does this information come from? Are there additional configuration files beyond nginx.conf and httpd.conf for the domains that include certificate information/path/location? This remains a mystery.