Hi UFHH01,
Thank you again for everything you do.
I am sorry for the delay but I have some personal issues.
Due to a lack of knowledge, I have some troubles following your solution. Why would I try to redirect each visitors to the The Plesk Control Panel => https://ONE-OF-YOUR-DOMAINS.COM:8443 ?
As you probably know, each visitor get two certificates while visiting our website (domain's certificate + Plesk's certificate). Thanks to you Plesk's certificate is now the same certificate as one of our firstwebsite.com and therefore this one does not have a problem anymore regarding the SSL certificate.
On the other hand, the secondwebsite.com do have a problem of certificate. Visitors get a warning message (not while they are visiting our website because Mozilla Firefox or Google Chrome are able to define the right certificate), but they do receive a warning message only when they receive an email to get their feedback.
To sum up, this problem is very hard to identify since we are not able to see while browsing the website. Recent navigators can define the right certificate and solve the bug automatically. We can identify it either by doing a SSL analyze with the website ssllabs that shows all the certificates related to the website, or in our case with the feedback's email that the website sends automatically.
Thank you again for everything you do.
I am sorry for the delay but I have some personal issues.
Due to a lack of knowledge, I have some troubles following your solution. Why would I try to redirect each visitors to the The Plesk Control Panel => https://ONE-OF-YOUR-DOMAINS.COM:8443 ?
As you probably know, each visitor get two certificates while visiting our website (domain's certificate + Plesk's certificate). Thanks to you Plesk's certificate is now the same certificate as one of our firstwebsite.com and therefore this one does not have a problem anymore regarding the SSL certificate.
On the other hand, the secondwebsite.com do have a problem of certificate. Visitors get a warning message (not while they are visiting our website because Mozilla Firefox or Google Chrome are able to define the right certificate), but they do receive a warning message only when they receive an email to get their feedback.
To sum up, this problem is very hard to identify since we are not able to see while browsing the website. Recent navigators can define the right certificate and solve the bug automatically. We can identify it either by doing a SSL analyze with the website ssllabs that shows all the certificates related to the website, or in our case with the feedback's email that the website sends automatically.