Username: larryk
TITLE
SSL issue
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS Linux 7.5.1804 (Core)
Product Plesk Onyx
Version 17.8.11 Update #95, last updated on Mar 9, 2021 03:19 AM
PROBLEM DESCRIPTION
After a domain SSL with Let's Encrypt has been working fine, randomly, a site will show this error
NET::ERR_CERT_COMMON_NAME_INVALID
To get Chrome’s highest level of security, turn on enhanced protection
ReloadHide advanced
www.test.com normally uses encryption to protect your information. When Google Chrome tried to connect to www.test.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be www.test.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.
You cannot visit www.test.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
NOTE: The first time I saw this: March 25, 2021.
To my knowledge, the sites where this happened, NOTHING was done on the site, domain, etc.
It just randomly happened.
Today, 5 sites have seen this problem out of 60.
While the simple, easy fix is to click the "Reissue certificate" button,
you can understand this is a HUGE, HUGE problem.
The site doesn't work and/or you DON"T want to see a big message saying... SSL Problem.
etc. etc.
STEPS TO REPRODUCE
it is random?
it just happens to some domains.
ACTUAL RESULT
on sites affected, you get the big error:
EXPECTED RESULT
the site should load up normally, all the time.
ANY ADDITIONAL INFORMATION
Question - Why did Let's Encrypted stop working, all of a sudden.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out
TITLE
SSL issue
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS Linux 7.5.1804 (Core)
Product Plesk Onyx
Version 17.8.11 Update #95, last updated on Mar 9, 2021 03:19 AM
PROBLEM DESCRIPTION
After a domain SSL with Let's Encrypt has been working fine, randomly, a site will show this error
Your connection is not private
Attackers might be trying to steal your information from www.test.com (for example, passwords, messages, or credit cards). Learn moreNET::ERR_CERT_COMMON_NAME_INVALID
To get Chrome’s highest level of security, turn on enhanced protection
ReloadHide advanced
www.test.com normally uses encryption to protect your information. When Google Chrome tried to connect to www.test.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be www.test.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.
You cannot visit www.test.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
NOTE: The first time I saw this: March 25, 2021.
To my knowledge, the sites where this happened, NOTHING was done on the site, domain, etc.
It just randomly happened.
Today, 5 sites have seen this problem out of 60.
While the simple, easy fix is to click the "Reissue certificate" button,
you can understand this is a HUGE, HUGE problem.
The site doesn't work and/or you DON"T want to see a big message saying... SSL Problem.
etc. etc.
STEPS TO REPRODUCE
it is random?
it just happens to some domains.
ACTUAL RESULT
on sites affected, you get the big error:
Your connection is not private
EXPECTED RESULT
the site should load up normally, all the time.
ANY ADDITIONAL INFORMATION
Question - Why did Let's Encrypted stop working, all of a sudden.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out