• 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 Plesk activation servers with wrong SSL cert?

Remco

New Pleskian
While trying to activate a new key, we get the error:
Error: cURL cannot communicate with license server https://id-00.kaid.plesk.com:5224/ (): Couldn't connect to server(7)
cURL cannot communicate with license server https://id-00.kaid.plesk.com:5224/ (): Couldn't resolve host name(6)

Executing curl by hand learned that the SSL certificate used is not valid for id-00.kaid.plesk.com
(curl: (51) SSL: no alternative certificate subject name matches target host name 'id-00.kaid.plesk.com')

Is there any issue with the SSL certificates?
 
Last edited:
Hi Remco,

yes, you are correct. The current certificate is issued for
Code:
CN = ka.odin.com
OU = Domain Control Validated
and not for "*.plesk.com"

Pls. consider to open a bug - report, explaining your steps-to-go to reproduce the issue at: => Home > Forum > Plesk Discussion > Reports
 
Back
Top