- Plesk for Windows
- Plesk for Linux
- License installation fails with one of the following errors:
PLESK_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)
PLESK_ERROR: Error: No properly formed ip addresses
PLESK_ERROR: Error: The license key is invalid. In order to use Plesk, you need to obtain and install a new valid license key. Your license key has expired. To continue using your Plesk, you must purchase a non-expiring commercial license key. Error: cURL cannot communicate with license server https://id-00.kaid.swsoft.com:5224/ (): Failed to connect to id-00.kaid.swsoft.com port 5224: Bad access(7) cURL cannot communicate with license server https://id-00.kaid.swsoft.com:5224/ (): Could not resolve host: id-00.kaid.swsoft.com(6)
PLESK_ERROR: ERR [panel] KeyUpdate Result additional information: cURL verbose output: * Trying 188.8.131.52... * connect to 184.108.40.206 port 5224 failed: Bad access * Failed to connect to ka.plesk.com port 5224: Bad access * Closing connection 0
- Cannot telnet to ka.plesk.com:
# telnet ka.plesk.com 5224
telnet: Unable to connect to remote host: Connection refused
Firewall on a server is blocking the connection to Plesk licensing server ka.plesk.com.
Since February 5, 2018, ka.plesk.com (KA, Key Administrator, a Plesk licensing server) hostname resolves to 3 different IP addresses based on round-robin:
- 220.127.116.11 (old one)
- 18.104.22.168 (new)
- 22.214.171.124 (new)
Additionally, since the same day KA accepts connections from Plesk on two ports:
- 5224 (old one, non-standard port)
- 443 (new, the default HTTPS port)
Plesk server should be able to establish connection to all three KA IP addresses and both KA ports in all their combinations (see the table below):
Allow connection to both ports on all IPs using Plesk interface:
- Login to Plesk
- Go to Plesk > Tools & Settings > Updates & Upgrades. In extensions section, select Plesk Firewall for installation.
- After installation, go to Tools & Settings > Firewall > Enable Firewall Rules Management > Enable
- By default, Plesk Firewall gets activated with the default list of rules, and connection to 5224 and 443 is allows by default. Make sure there is the following line in Plesk Firewall set to be allowed:
CONFIG_TEXT: System policy for outgoing traffic
Allow connection using SSH connection:
- Log in to the server over SSH
- Add the following rules to the local firewall. For example, iptables:
# iptables -I OUTPUT -p tcp -d 126.96.36.199,188.8.131.52,184.108.40.206 -m multiport --dports 443,5224 -j ACCEPT
# iptables -I INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
- Check the Key Administration server connectivity:
# telnet ka.plesk.com 5224
# telnet ka.plesk.com 443
For Amazon AWS:
If using Amazon AWS, visit this article to learn how to open the connection to a port and IP address:
How to open inbound connection to port for AWS
For Google Cloud:
- Login to Google Cloud account
- Navigate to VPC network > Firewall rules > Create firewall rule
- Set Direction of traffic to be Egress.
- Set Action on match to be Accept.
- Set Targets to be All instances in the network.
- Allow access to
ka.plesk.comby setting Destination IP ranges field to 220.127.116.11
(Repeat the same for 18.104.22.168 and 22.214.171.124)
- Set Protocols and ports field to be tcp:5224.
(Repeat the step for tcp:443)
- Click Create.
If issue is not solved, contact network administrator or server owner in order to allow connection to all of those IPs/ports in a server and intermediary (or third-party) firewall.