• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Your connection isn't private NET::ERR_CERT_DATE_INVALID

fatimah_qadheeb

New Pleskian
I am using Plesk to host my website. I am seeing this error when I try to login to my Plesk server account. It is not allowing me to log in and showing this error

Your connection isn't private​

Attackers might be trying to steal your information from optimistic-t.plesk.page (for example, passwords, messages or credit cards).
NET::ERR_CERT_DATE_INVALID
Subject: optimistic-t.plesk.page
Issuer: Let's Encrypt Authority X3
Expires on: 27 Jan 2021
 
I have followed the link you provide me but when I create a Let's Encrypt certificate for Plesk it shows this error

Error: Could not request a Let's Encrypt SSL/TLS certificate for optimistic-tu.MY-IP-ADDRESS.plesk.page.

Go to http://optimistic-tu.MY-IP-ADDRESS.plesk.page/.well-known/acme-challenge/THEKEY
and сheck if the authorization token is available.
If it is, try to request the certificate again. If the token is not available, there may be an issue with your DNS configuration.
Your domain in Plesk is hosted on the IP address(es): , but the DNS challenge used another IP:

Eventhgouh, I have used the subdomain certificate for securing Plesk and it works successfully.

But still, the HTTPS request to Plesk shows an error this connection is not private
 
Back
Top