Issue Send report to plesk supprt

[Dork]

Server operating system version

CentOS Linux 7.9.2009

Plesk version and microupdate number

18.0.56

report failed: Failed to send report: Failed connect to ka.plesk.com:443; Operation now in progress

How to repair that?

 

[Peter Debik]

The error can mean that DNS does not resolve ka.plesk.com correctly.

What is the result of
# plesk bin license --retrieve
?

What is the result of
# curl https://ka.plesk.com/jsonrest/pkp/20/verify-key
?
(If the result is "Authorization failed" it would be alright.)

 

[Dork]

plesk bin license --retrieve
result:
Updating Plesk license key: [2023-10-14 22:25:53.580] 24850:652af9141a320 ERR [panel] KeyUpdate Result code: 2 Network failure
[2023-10-14 22:25:53.580] 24850:652af9141a320 ERR [panel] KeyUpdate Result desc: cURL cannot communicate with license server https://ka.plesk.com/xmlrpc (195.214.233.81): Couldn't connect to server(7)
cURL cannot communicate with license server https://ka.plesk.com/xmlrpc (): Couldn't resolve host name(6)
[2023-10-14 22:25:53.581] 24850:652af9141a320 ERR [panel] KeyUpdate Result additional information: cURL verbose output:
* About to connect() to ka.plesk.com port 443 (#0)
* Trying 195.214.233.80...
* After 29998ms connect time, move on!
* Trying 195.214.233.82...
* After 14998ms connect time, move on!
* Trying 195.214.233.81...
* After 7498ms connect time, move on!
* Failed connect to ka.plesk.com:443; Operation now in progress
* Closing connection 0

cURL verbose output:
* Could not resolve host: ka.plesk.com; Unknown error
* Closing connection 1

Could not update the license. Make sure that connections to the license server ka.plesk.com on TCP port 443 are not blocked. To fix the issue, follow the instructions described in KB https://support.plesk.com/hc/en-us/articles/12388137260695.

But the KB url leads to a non existing page

 

[Peter Debik]

I can open https://support.plesk.com/hc/en-us/articles/12388137260695 over the public Internet here without issues. Please try again. The above shown error shows an issue with domain name resolution. Is this a server in your local network? As you cannot access the support article, this could mean that there is a broader issue with name resolution in your local network.