• 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

Issue License Problem

bequiet

New Pleskian
Hey guys,

my plesk wont update my license correctly.

"Could not update the license. Make sure that connections to the license server ka.plesk.com on TCP port 443 are not blocked." - says my Servers.
I followed every KB Article.

If I try to update the license via ssh then I get "Could not resolve host: id-00.kaid.plesk.com" - but on ssh I connect via curl & telnet.

Telnet Connections are successfull to ka.plesk.com and id-00.kaid.plesk.com on port 443. I get correct nslookup entries and also my dig requests are successfull.
 
What nameserver do you have specified in /etc/resolv.conf file?
Try to comment all there and leave only record like:
Code:
nameserver 8.8.8.8
 
i have same problem with my plesk.
my server can resolve id-00.kaid.plesk.com


root@hosting:~# nslookup id-00.kaid.plesk.com
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
id-00.kaid.plesk.com canonical name = ka.plesk.com.
Name: ka.plesk.com
Address: 195.214.233.81
Name: ka.plesk.com
Address: 195.214.233.82
Name: ka.plesk.com
Address: 195.214.233.80

and i can telnet to id-00.kaid.plesk.com on port 443

root@hosting:~# telnet id-00.kaid.plesk.com 443
Trying 195.214.233.81...
Connected to id-00.kaid.plesk.com.
Escape character is '^]'.

but when i want install license on server in panel.log i getting this messege:

[2022-02-20 16:09:04.825] 4853:62123629402d7 ERR [panel] KA Request Failure code: 2 Network failure
[2022-02-20 16:09:04.825] 4853:62123629402d7 ERR [panel] KA Request Failure desc: cURL cannot communicate with license server https://id-00.kaid.plesk.com:443/ (195.214.233.81): Timeout was reached(28)
cURL cannot communicate with license server https://id-00.kaid.plesk.com:443/ (): Couldn't resolve host name(6)
 
Same symptom, but maybe different cause. In the example displayed by @bequiet no public IPv4s were associated with the server. Is that the same case in your system? The server's name (hostname) must be publicly accessible, meaning that it must be associated with a valid public IP address.
 
The public IP address is on server and associated with hostname.
when i nslookup my server host name by 8.8.8.8 that return my public ip address assigned on nic of server
 
Back
Top