• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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