Resolved Plesk Onxy 17.5, license not updated, feedback- instead of key-server accessed ?

[Klaus W. Otto]

Hello,

we are using the latest version of Plesk Onyx 17.5.x on serveral CentOS 6.9 and 7 servers. On two of the CentOS 6.9 servers the license key is no longer updated. On other servers with the same environment it still works.

If you try to update the key on the affected servers via Plesk panel the page won't refresh and you get the nginx message "504 Gateway Time-out".

Using "plesk bin license --retrieve" on console leads to a cURL timeout message.

The three Plesk key servers ka.plesk.com (195.214.233.80, 195.214.233.81, 195.214.233.80) are not blocked by a firewall and can be accessed via curl and telnet on port 5224 and 443.

After quite some time and work it seems that the working servers still sync their keys with ka.plesk.com on port 5224 whereas the two non-working servers try to connect to feedback.pp.plesk.com on port 443.

So my question is...
Is Plesk testing some new update mechanism or is there something wrong with our server configuration?
What can or has to be done?

One of the two affected keys has to be prolonged in 4 days so it would be nice if someone from Plesk could answer.

Thank you!


tcpdump port 5224 (on working server)

2:07:31.553940 IP ka.plesk.com.hpvirtctrl > <REMOVED>.43230: Flags [P.], seq 4767:4842, ack 321, win 130, options [nop,nop,TS val 2166407298 ecr 5556516], length 75
12:07:31.554204 IP <REMOVED>.43230 > ka.plesk.com.hpvirtctrl: Flags [P.], seq 321:1670, ack 4842, win 137, options [nop,nop,TS val 5556534 ecr 2166407298], length 1349
12:07:31.610921 IP ka.plesk.com.hpvirtctrl > <REMOVED>.43230: Flags [.], ack 1670, win 151, options [nop,nop,TS val 2166407356 ecr 5556534], length 0
12:07:31.994707 IP ka.plesk.com.hpvirtctrl > <REMOVED>.43230: Flags [P.], seq 4842:5199, ack 1670, win 151, options [nop,nop,TS val 2166407740 ecr 5556534], length 357
12:07:31.994744 IP ka.plesk.com.hpvirtctrl > <REMOVED>.43230: Flags [FP.], seq 5199:5252, ack 1670, win 151, options [nop,nop,TS val 2166407740 ecr 5556534], length 53
12:07:31.995110 IP <REMOVED>.43230 > ka.plesk.com.hpvirtctrl: Flags [P.], seq 1670:1723, ack 5253, win 160, options [nop,nop,TS val 5556974 ecr 2166407740], length 53
12:07:31.995143 IP <REMOVED>.43230 > ka.plesk.com.hpvirtctrl: Flags [R.], seq 1723, ack 5253, win 160, options [nop,nop,TS val 5556975 ecr 2166407740], length 0
12:07:32.011682 IP ka.plesk.com.hpvirtctrl > <REMOVED>.43230: Flags [R], seq 3073774158, win 0, length 0

tcpdump port 443 (on non-working server)

12:09:53.468143 IP <REMOVED>.35308 > feedback.pp.plesk.com.https: Flags [.], seq 673:3569, ack 2821, win 137, options [nop,nop,TS val 927943 ecr 2174961065], length 2896
12:09:53.468181 IP <REMOVED>.35308 > feedback.pp.plesk.com.https: Flags [.], seq 3569:6465, ack 2821, win 137, options [nop,nop,TS val 927943 ecr 2174961065], length 2896
12:09:53.484936 IP <REMOVED>.35308 > feedback.pp.plesk.com.https: Flags [P.], seq 6465:7174, ack 2821, win 137, options [nop,nop,TS val 927960 ecr 2174961082], length 709
12:09:53.541506 IP feedback.pp.plesk.com.https > <REMOVED>.35308: Flags [.], ack 7174, win 184, options [nop,nop,TS val 2174961139 ecr 927960], length 0
12:09:53.611362 IP feedback.pp.plesk.com.https > <REMOVED>.35308: Flags [P.], seq 2821:3034, ack 7174, win 184, options [nop,nop,TS val 2174961208 ecr 927960], length 213
12:09:53.611697 IP <REMOVED>.35308 > feedback.pp.plesk.com.https: Flags [P.], seq 7174:7211, ack 3034, win 160, options [nop,nop,TS val 928086 ecr 2174961208], length 37
12:09:53.614323 IP <REMOVED>.35308 > feedback.pp.plesk.com.https: Flags [F.], seq 7211, ack 3034, win 160, options [nop,nop,TS val 928089 ecr 2174961208], length 0

 

[Klaus W. Otto]

I've checked key updates this morning and they were not working. Only the feedback-server was accessed.

I've checked it again ten minutes ago and now updates are working again.
Feedback-server AND key-server are now accessed and cURL timeout message is gone.

It seems Plesk is still testing.

 

[Sergio Manzi]

I see this is flagged as resolved, but no explanation on the "how" is given: is it really solved? If not, I think you're better off contacting Plesk support for this kind of issue...