- Plesk for Linux
- Plesk for Windows
Domain that is hosted on a Plesk server cannot be opened over HTTPS at https://example.com, it shows the following warnings
In Chrome browser:
CONFIG_TEXT: Your connection is not private
Attackers might be trying to steal your information from example.com (for example, passwords, messages, or credit cards). Learn more
This server could not prove that it is example.com; its security certificate is from *.example.com. This may be caused by a misconfiguration or an attacker intercepting your connection.
Proceed to example.com (unsafe)
In Firefox browser:
CONFIG_TEXT: Your connection is not secure
The owner of example.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.
example.com uses an invalid security certificate. The certificate is only valid for *.example.com Error code: SSL_ERROR_BAD_CERT_DOMAIN
curl request shows:
# curl -v https://example.com/
* About to connect() to example.com port 443 (#0)
* Trying 203.0.113.2... connected
* Connected to example.com (203.0.113.2) port 443 (#0)
* NSS error -12276
* Closing connection #0
curl: (51) SSL: certificate subject name '*.example.com' does not match target host name 'example.com'
Any public SSL checker shows:
CONFIG_TEXT: Common name: *.example.com
SSL certificate installed for the domain doesn't contain a domain name (example.com), a subdomain name (*.example.com) or a domain aliases (alias-example.com).
If domain is secured with SSL certificate via Plesk Let's Encrypt extension:
Visit this article to re-create (re-issue) SSL for a correct domain name: How to install SSL certificate for a domain in Plesk
To learn how to secure domain alias, visit: How to install Let's Encrypt certificate for domain alias
If domain is secured with SSL certificate issued by a side SSL issuer (outside of Plesk):
Contact that SSL certificate provider in order to re-issue SSL for example.com: SAN name should include base domain name (example.com).