Hi Philipp,
No, the issue was not officially resolved. However, Google did not continue to send warnings.
The SNI configuration and Let's Encrypt SSL certificate (both managed by Plesk) appears to be correct. The problem is originating in the Google client that sends a non-SNI request for...
Hi Peter,
Thanks again for your help!
2 VPS servers (2 different providers) are a default Plesk server, recently upgraded to Plesk Onyx. How could IPv6 be incorrectly configured?
One of the VPSes is especially default, CentOS 7 + Plesk. It simply had domains added to it with a WordPress...
Hi Peter,
Thank you for the technical insight!
As for a fix: the problem is Google / SEO. Google is not sending a warning for an invalid certificate if it does not use that information in it's system to list a website in the search results. It may lead to a drop in traffic, damage to the...
Hi Peter,
Thank you for your response!
On several websites we used Plesk to install a Let's Encrypt certificate. The SSL score on SSLLabs.com is A (good) and no issues are shown. However, Google does warn for a self-signed certificate.
I've read all topics to find a solution. Advanced server...
Should I go somewhere else for support / to report a critical bug? I am suspecting that many users may be at risk of SEO damage because of this Plesk bug.
Dear Plesk Support,
Since a few days ago I started using the Let's Encrypt extension for Plesk Onyx to provide a free SSL certificate for several domains.
One of the servers is a VPS with 1 IP (no ability to add IP's) and SSL is used via SNI.
Directly after installing an SSL certificate for...