• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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