Parallels Plesk Powerpack AMI Licensing Issue

[NorbertA]

Hello everybody,

I've spent the whole day figuring out how to get the correct license in my new Amazon EC2 instance. I used the PowerPack AMI which says it includes a license (and it charges $0.07/hour for it). For some reason, Plesk gives me a warning that I am operating within the license grace period and cannot host more than 1 domain.

Could anyone advise me on this situation?

 

[NorbertA]

While I realize that I am not an enterprise costumer with 1000 VM's running Plesk, I still pay for a license which is not working. The support desk referred me to Amazon because it is on their cloudservice, the Amazon support desk referred me to Parallels because they sell the Amazon Machine Image on the AWS Marketplace themselves. I'm kind of stuck here and would really appreciate a reply from a Parallels support engineer/customer service representative.

Also, *bump*.

 

[IgorG]

The support desk referred me

If I correctly understood you have submitted ticket to Parallels Support Team? Could you please provide me id of this ticket? I will check it.
Also I recommend you contact Parallels sales representative from nearest Parallels office - http://www.parallels.com/about/contact/
They will help you with licensing questions much more effectively.

 

[IgorG]

BTW, I can add following. There two scenarios are possible:

1. You buy image with Plesk in the Amazon marketplace. In that case when you start instance first time internal master key will be updated to usual working power-pack key.

2. You deploy Plesk server from our image which was published. In that case you should buy key by yourself.

 

[NorbertA]

Thank you for your response Igor. My ticket number is #1561353. You described two scenario's, I am using the AMI with the included master key: Parallels Plesk Panel 11.0.9 with MasterKey_(PowerPack)-44a3a9dd-479f-4131-afa0-19bfdeb23a2e-ami-1356db7a.1 (ami-0a2f237e).

However, when I try to retrieve the keys via the License Management page, I get the following error:

Request cannot be serviced from the specified IP(s): [left out my IP address].

I also get an e-mail with the following message each time I try to update the key:

Unable to update PLSK[keynumber]. An error occurred while processing your key. You can try updating it later.

 

[IgorG]

This confirms the fact that you need to talk with a sales representative.

 

[NorbertA]

I just wanted to say I fixed the problem by redeploying the AMI, and not running the "yum update" command as described in the setup manual. For some reason, the update procedure kept screwing up my license key.

 

[NicksterFL]

I'm having the same problem. Just signed up for AWS EC2 with Plesk with PowerPack. But when I log into Plesk it says "Warning you are currently operating within a grace period of your product license"
When I go to the License Management area it says "

"Request cannot be serviced from the specified IP(s): xx.xx.xx.xx"

 

[SGISoft]

Hello,
I have had the same problem as you.
Onix 17.8 and Debian 9
In my case I had 2 IPs, the main one and an extra for a particular website.

When I tried to update the license it gave me that the error occurred when trying to update with the secondary IP.

My configuration:

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
ether --:--:--:--:--:-- txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet XXX.XXX.XXX.XXX netmask 255.255.255.255 broadcast XXX.XXX.XXX.XXX
inet6 XXX::XXX:XXX:XXX:XXX prefixlen 64 scopeid 0x20<link>
inet6 XXX:XXX:XXX:XXX::XXX:XXX prefixlen 64 scopeid 0x0<global>
ether --:--:--:--:--:-- txqueuelen 1000 (Ethernet)
RX packets 79274766 bytes 15336823671 (14.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 139467060 bytes 195826565829 (182.3 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdf900000-df920000

eth0:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet YYY.YYY.YYY.YYY netmask 255.255.255.255 broadcast YYY.YYY.YYY.YYY
ether --:--:--:--:--:-- txqueuelen 1000 (Ethernet)
device interrupt 16 memory 0xdf900000-df920000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 27422843 bytes 252377048893 (235.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 27422843 bytes 252377048893 (235.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Error:

ERR [panel] KeyUpdate Result desc: Request cannot be serviced from the specified IP(s): YYY.YYY.YYY.YYY
ERR [panel] KeyUpdate Result code: 2 Unspecified error

The fastest and least painful way to perform the update is to disable the second IP temporarily, update the key and re-raise the secondary IP:
ifdown eth0:1 ; plesk bin license --retrieve ; ifup eth0:1

If someone comes up with another better way it would be great. At the moment I'm going to leave it like that until the next renewal and I see if it is necessary to create a cron so that I do it manually every so often.