• 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

Cannot install or retrieve license key

C

craigueH

New Pleskian
We have about 8 VPS servers that are recently failing to install or update their license keys.
When we try to update the key it hangs for about 15 minutes and then fails with 504 gateway timeout.

We can ping ka.odin.com and it resolves to the correct ips etc. from each server.
Reboots don't seem to help and neither does installing the license from a file.

Any advice would be appreciated.
Thanks
 
Try to do it manually in CLI with enabled debug mode:

# export PLESK_DEBUG=1
# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f UpdateKeys

And check possible error messages in output.
 
I did this on several Plesk 12 servers and there is nothing in the output, it just hangs for about 10 minutes and then finishes with no feedback and the license still doesn't update.

We are also seeing a similar issue on our Plesk Automation CP now aswell when trying to update the license.

Unable to connect to license server https://ka.odin.com:5224/xmlrpc.
cURL error description: Server returned nothing (no headers, no data)(52)

I can ping ka.odin.com and I can run "curl https://ka.odin.com:5224/xmlrpc" but it comes back with a certificate error.
We have run all Plesk microupdates and CentOS updates on these servers but that didn't help.
 
Ok, now feom a Plesk VPS when I try to run the following:

./license -i A00800-xxxxx-yyyyy-zzzzz

I get this error after about 15 minutes:
Curl failed: Timeout was reached
Unable to connect to license server https://id-00.kaid.swsoft.com:5224/.
cURL error description: Failed sending data to the peer(55)

However, I can ping the id-00.kaid.swsoft.com domain and I added a host entry to be sure.
Running "curl https://id-00.kaid.swsoft.com:5224/" returns the same certificate error as the previous post.
 
Are you sure that port 5224 is not firewalled? Have you checked connection with telnet, for example?
 
Port 5224 is definitely not firewalled and running the following from the command line gets a response:

curl https://id-00.kaid.swsoft.com:5224/
curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.


And running this with -k gets the following:

curl -k https://id-00.kaid.swsoft.com:5224/
<html><head><title></title></head><body>HTTP status code 403<br/>Only PKP XML-RPC requests to /xmlrpc and JSON-REST requests to /jsonrest/pkp are allowed on port 5224</body></html>
 
swsoft.com ??? This company does not exist a lot of years. What is your Plesk version? We are Plesk now and our Key Administrator address is ka.plesk.com
 
You must log in or register to reply here.

Similar threads

M
Resolved Cannot install or retrieve license key
2
Replies
22
Views
10K
mazo0012
M
A
Question Upgrade Almalinux 8 to 9 with Plesk installed
Replies
2
Views
443
ansgar
A
G
Question WP installs are quarantined daily.
Replies
4
Views
656
Bobbbb
B
K
Issue Plesk/Something removes all /etc/httpd/conf/plesk.conf.d/vhosts/ configs on reboot
Replies
0
Views
498
kevinjansen
K
Lenny
Resolved Seeking Assistance with API Communication Issues via SSL on Plesk
Replies
4
Views
711
Lenny
Lenny
Back
Top