SSL Certificates incorrect for Plesk Activation Servers

[Remco]

TITLE:

SSL Certificates incorrect for Plesk Activation Servers​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk Onyx 17.5.3​

PROBLEM DESCRIPTION:

Entering a new activation key throws an 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)

When executing curl by hand or opening the url in the browser will show that the SSL certificate doesn't belong to the *.plesk.com servers.​

STEPS TO REPRODUCE:

Tools & Settings / Plesk / License Management / Install Key​

ACTUAL RESULT:

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)

Results for manual curl:

curl https://id-00.kaid.plesk.com:5224/
curl: (51) SSL: no alternative certificate subject name matches target host name 'id-00.kaid.plesk.com'​

EXPECTED RESULT:

Successful activation​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[UFHH01]

Hi Remco,

even that the certificate for the domain doesn't match, you should still be able to activate the license, Pls. make sure, that you opened the needed ports ( if you use a firewall on your server ) and pls. make sure, that you are able to resolve the host ( pls. check as well your "/etc/resolv.conf" ) from your command line.

=> Which Ports Need To Be Opened for all Plesk Services to Work with a Firewall?​

 

[AYamshanov]

cURL cannot communicate with license server https://id-00.kaid.plesk.com:5224/ (): Couldn't resolve host name(6)

This is Linux? Could you show /etc/resolv.conf and check that nameserver are correct and workable. I think the problem in nameserver from /etc/resolv.conf.

 

[Remco]

Issue was solved by UFHH01's suggestion. It's seemed it was a firewall somewhere in the network blocking the port

Apologies for troubling you, this issue can be marked as solved.