Issue Secure https is not working for and subscriptions/sites

[davewnz]

I have setup and created a Lets Encrypt server certificate, this worked for the Plesk server on port 8443.

No sites in any subscriptions will work for https even when trying to access webmail using https.

I have tried a lot of suggestions including removing all certs for all subscriptions and the server (except the original default one) - and then recreating using Lets Encrypt. The certs get generated correctly - and i can assign the correct certs including for webmail etc with no errors.

I have also switched the MPM mode from Event to Prefork as suggested also in one post.

On visiting https: all i see is 'ERR_CONNECTION_CLOSED'

In the sites log is see...

[ssl:warn] [pid 11460] AH01909: example.com:443:0 server certificate does NOT include an ID which matches the server name

If i check the cert: sudo openssl x509 -in cert-XXXXXX -noout -subject

I see the correct sites name as subject= /CN=example.com

In /var/log/apache2/error.log i see:

[ssl:warn] [pid 7317:tid 139701702813568] AH01909: webmail.example.com:443:0 server certificate does NOT include an ID which matches the server name.

I have rebuilt all config files - and on checking these they do appear to look correct.

Does anyone have any ideas on what else i can check in Plesk as this is driving me nuts!!.



OS ‪Ubuntu 16.04.3 LTS‬
Product Plesk Onyx
Version 17.5.3 Update #24, last updated on Oct 9, 2017 10:07 AM
The system is up-to-date. Checked on Oct 8, 2017 06:25 AM.

 

[IgorG]

In most cases, this warning (NOT ERROR!) means that CN parameter of the certificate installed on domain does not match value of ServerName directive specified in the corresponding VirtualHost configuration. Please check that there is the same value.

 

[davewnz]

In most cases, this warning (NOT ERROR!) means that CN parameter of the certificate installed on domain does not match value of ServerName directive specified in the corresponding VirtualHost configuration. Please check that there is the same value.

Thanks, though as i mentioned in my comment, i did check the cert applied to a site and i do see the correct sites name as subject= /CN=example.com. So i think the problem is not at the site cert level?

 

[IgorG]

But are you sure that ServerName parameter of Vhost configuration has the same value as in /CN?
And I suppose that this warning may be ignored. Mostly this affects nothing.