• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved SSL Certificate Error for domain mail

RobertoMa

Basic Pleskian
Hello,
i have Plesk 18.0.41 on my Virtual Server.
My server host Is: server.example.com
i have also added other domain with certificate wildcard and i added in domain mail setting the certificate. The SNI is active.
my problem is that when add mail [email protected] in client i have message certificate not safe.

the configuration DNS of domain.com is:

domain.com A ipserver
domain.com MX 10 mail.domain.com
mail.domain.com CNAME domain.com

i tried also put MX record to server.example.com but i have same error.
Please help me.
 
This is solely a client issue. When the client still uses an expired root certificate, the validity of Let's Encrypt certificates cannot be checked. The check will always fail. For that reason you are seeing this issue only on that very one client. You need to update the root certificates on the client. This is normally done by an operating system update, e.g. an Android upgrade.
 
This is solely a client issue. When the client still uses an expired root certificate, the validity of Let's Encrypt certificates cannot be checked. The check will always fail. For that reason you are seeing this issue only on that very one client. You need to update the root certificates on the client. This is normally done by an operating system update, e.g. an Android upgrade.

My device has last version of Android.
 
Back
Top