• 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.

Resolved RSA server certificate warning

David Jimenez

Basic Pleskian
A few times a day I see the following in our server logs and don't know what this really means.

RSA server certificate CommonName (CN) `Plesk' does NOT match server name!?

I am sure it is a setting somewhere that I don't know about and hoping someone can point me in the right direction.

Thanks
 
Hi David Jimenez,

I assume I can call the self-signed certificate anything I want
Well, ...no. The command "do echo" will not generate NEW certificates, it will just insert the SUBJECT - definition(s) to the existing certificates, found at "/usr/local/psa/var/certificates/". I'm really not sure, what you you would like to "call" or "name" here?
 
i used the part of the KB talking about creating a new certificate. I chose self-signed and just named it the same as our domain. I made it the default and then selected it in the hosting security section. This seems to have worked as no error messages in the past 10+ hours.
 
Back
Top