License key update fails on OpenSuSE 11.1

[IgorG]

I have exactly the same problem but on debian lenny.

I updated from psa 9.3.0 (debian etch) to psa 9.5.1 (debian lenny).
Now my panel is blocked and when i try to retrieve the key it just says "Software Update Service (SUS) is not found for the given license key. Automatic upgrade is not possible "

I tried to use the old versions of openssl / libcurl, but if I do so the panel is not reachable (error 500).
Has anyone a solution? Is there a CLI option for key retrieval?

Thanks in advance.

Could you please provide me license key number? Utility for automatic key retrieving is /usr/lib64/plesk-9.0/key-upgrade (w/o options)

 

[pstadler]

Hi IgorG

My friend talked to a parallels sales person and was told that we need a new license. Now with the new license everything works again but I'm kind of confused because I thought our original license was for the whole 9.x series.

Let me quote what he wrote:

Per records the License key <number-hidden> is for 9.x and which is from 9.0 to 9.3.

Please advised that 9.5 is a upgrade, but not a update. If you have upgraded the server to 9.5 version the 9.x License would not be a valid key.

Further you would have to upgrade the License key <number-hidden> to 9.5 versions; in order to upgrade to 9.5 your License should have valid SUS (Software Update Service) which would help you to upgrade to the latest version.

As per our records the License key <number-hidden> does not have SUS on it,
so it is advised to buy Reinstatement of SUS on your License and then upgrade the License to 9.5.

However your versioning is pretty confusing if not even misleading as "per records the License key <number-hidden> is for 9.x and which is from 9.0 to 9.3."... hell yeah! But hey, it was definitely our fault because our license had no valid SUS and 9.5 is an upgrade and not an update. Hopefully our license doesn't need a valid JE-SUS to unblock the Panel when we update... errrm sorry, upgrade to 9.6 ;-)

Thank you anyway.

Patrick

 

[MiguelK]

Same Problem

Hello!

I am with the same problem here...
Using openSUSE 11.1

# host ka.parallels.com
ka.parallels.com has address 64.131.90.38


# fping -c 4 ka.swsoft.com
ka.swsoft.com : [0], 96 bytes, 96.0 ms (96.0 avg, 0% loss)
ka.swsoft.com : [1], 96 bytes, 92.0 ms (94.0 avg, 0% loss)
ka.swsoft.com : [2], 96 bytes, 96.0 ms (94.6 avg, 0% loss)
ka.swsoft.com : [3], 96 bytes, 96.0 ms (95.0 avg, 0% loss)

ka.swsoft.com : xmt/rcv/%loss = 4/4/0%, min/avg/max = 92.0/95.0/96.0
# openssl s_client -connect ka.swsoft.com:5224 -tls1
CONNECTED(00000003)
14713:error:140943F2:SSL routines:SSL3_READ_BYTES:sslv3 alert unexpected message:s3_pkt.c:1087:SSL alert number 10
14713:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:530:

# /usr/lib64/plesk-9.0/key-upgrade; echo $?

1

# zypper install -f openssl openssl-certs
Carregando dados de repositrio...
Lendo os pacotes instalados...
Resolvendo dependncias de pacote...

Os seguintes pacotes sero reinstalados:
openssl openssl-certs


Tamanho total do download: 606,0 K. Nenhum espao adicional ser usado ou liberado aps a operao.
deseja continuar? [SIM/No]: sim
Recuperando pacote openssl-0.9.8h-28.15.1.x86_64 (1/2), 493,0 K (1,1 M descompactado)
Instalando: openssl-0.9.8h-28.15.1 [CONCLUDO]
Recuperando pacote openssl-certs-0.9.8h-25.2.19.noarch (2/2), 113,0 K (190,0 K descompactado)
Instalando: openssl-certs-0.9.8h-25.2.19 [CONCLUDO]
# openssl s_client -connect ka.swsoft.com:5224 -tls1
CONNECTED(00000003)
15071:error:140943F2:SSL routines:SSL3_READ_BYTES:sslv3 alert unexpected message:s3_pkt.c:1087:SSL alert number 10
15071:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:530:

I can't downgrade libcurl (like http://kb.odin.com/en/6096).

And I got errors when trying to update to 9.3.1 or 9.5+

What can I do now?

Any solution?

Thank you very much,

Miguel Koscianski Vidal

 

[MiguelK]

My Plesk Panel are blocked...
I can't manage my server, domains, etc....

What I need to do to solve this???

Please, anyone help me...

Thank you very much,

Miguel Koscianski Vidal

 

[MiguelK]

Will the Plesk Panel be blocked after some time?

Now with this error message:
"Error: The license key is invalid. In order to use the Parallels Plesk Panel, please obtain and install a new functioning license key.
Your license key has expired. To continue using your Parallels Plesk Panel you must purchase a non-expiring commercial license key."

What should I do?

Thank you very much,

Miguel Koscianski Vidal

 

[MiguelK]

Will the Plesk Panel be blocked after some time?

Now with this error message:
"Error: The license key is invalid. In order to use the Parallels Plesk Panel, please obtain and install a new functioning license key.
Your license key has expired. To continue using your Parallels Plesk Panel you must purchase a non-expiring commercial license key."

What should I do?

Thank you very much,

Miguel Koscianski Vidal

 

[LucillaV]

I have the same problem. I tried the suggestion of Christian Gassmann but I get the same message:

Warning: You are currently operating within the grace period of your product license. To update your product license, select the Retrieve Keys option on the License Management page.


and when I select the option Retrieve Keys I get:

Key Update Status
SSL connect error

My Key expiration date is June 12, 2010 !!!!!

What I must do to resolve?

 

[glenkinchie]

The newest plesk update seems to resolved that problem.

 

[LucillaV]

The newest plesk update seems to resolved that problem.

YES!!! update to 9.5.2 and the license key update is OK!!

thanks

 

[WernerD]

same error after SUSE Update with YOU

After SUSE YOU Update (security Updates) I get the plesk key can't be updated: (SUSE 11.1 - 64 bit / PLESK 9.3)

/var/log/sw-cp-server/error_log:

2010-12-18 08:20:10: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure.
2010-12-18 08:25:29: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure.
2010-12-18 08:26:42: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure.

curl -k -ssl3 https://ka.parallels.com:5224

* About to connect() to ka.parallels.com port 5224 (#0)
* Trying 64.131.90.38... connected
* Connected to ka.parallels.com (64.131.90.38) port 5224 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using DHE-RSA-AES256-SHA
* Server certificate:
* subject: /C=US/O=ka.plesk.com/OU=Business Registration: https://services.choicepoint.net/get.jsp?4110196571/OU=See www.geotrust.com/quickssl/cps (c)03/OU=Domain Control Validated/CN=ka.plesk.com
* start date: 2003-08-21 06:21:43 GMT
* expire date: 2004-10-20 06:21:43 GMT
* common name: ka.plesk.com (does not match 'ka.parallels.com')
* issuer: /C=US/O=Equifax/OU=Equifax Secure Certificate Authority
* SSL certificate verify result: certificate has expired (10), continuing anyway.
> GET / HTTP/1.1
> User-Agent: curl/7.19.0 (x86_64-suse-linux-gnu) libcurl/7.19.0 OpenSSL/0.9.8h zlib/1.2.3 libidn/1.10
> Host: ka.parallels.com:5224
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Length: 1159
< Date: Sat, 18 Dec 2010 07:45:20 GMT
<
<html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 403 - Only PKP XML-RPC requests to /xmlrpc are allowed on the port 5224</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Only PKP XML-RPC requests to /xmlrpc are allowed on the port 5224</u></p><p><b>description</b> <u>Access to the specified resource (Only PKP XML-RPC requests to /xml* Connection #0 to host ka.parallels.com left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
rpc are allowed on the port 5224) has been forbidden.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html>