Plesk Control Panel after Automatic Key Update

[SpidermonBob]

I have been unable to login to my Plesk Control Panel (https://xxx.xxx.xxx.xxx/8443) and noticed the following emails* which indicated that a failure to automatically update the Plesk key has some how shutdown Plesk. I tried to contact tech support and was told to try "telnet ka.swsoft.com 5224" which produced the following result "64.131.xxx.xxx... Connected to ka.soft.swsoft.com" …so apparently the port is open.

I was soon informed by tech support that since I did not have a current support contract that they could not help me to restart Plesk.

I find it absurd that Plesk forces an update to my keys that shuts down my server and no one at tech support can provide me the simple information as to how to restart my server after the automatic key update failed.



*Email from my server.....


I received the following email from my server...
------------>>
There were problems while trying to update your Plesk key.
Plesk will continue trying.
Details:

Licensing Server Unreachable: Unable to connect with licensing server.
Please make sure that your network allows communication to ka.swsoft.com:5224.
For more details check system help pages.
<<------------------


I then received the following email from Watchdog on my server:
------------>>
The Plesk Web Server service on host www. MyDomain.com is down.
The problem was discovered on Dec xx, 2007 01:13 PM.
<<------------------


I then received the following email from Watchdog on my server:
------------>>
The Plesk Web Server service on host www.MyDomain.com has been released from monitoring on Dec 28, 2007 01:38 PM.
<<------------------




In attempting to solve the problem I found the Article ID: 118 - How do I restart Plesk… Apparently this is not the correct path structure for my Debian Sarge server since I get the error “No such file or directoryâ€

I then tried /etc/init.d/psa start … and apparently that starts various processes and indicates “Starting Plesk… done†but “Starting drwebd service… failed†…When I try to again to login to my Plesk Control Panel I am still unable to access the login page because of a timeout.

Can anyone please help me with this problem?

 

[Amin Taheri]

Wow, that sucks.

Try looking into the Key stuff in SSH, not sure if this will help or not

/usr/local/psa/bin/keyinfo
/usr/local/psa/admin/sbin/keymng

 

[chep]

Did this ever get resolved?

I am getting similar emails and wonder if I will be soon locked out of my server.

 

[pdws]

Guys,

First of all you need to make sure that:

The port 5224 is open and that the "ka.swsoft.com:5224" is accessible.

If it's not filtered and the license is not a lease one (monthly billing)

These two articles may be of help as well:

http://kb.swsoft.com/en/462

http://kb.swsoft.com/en/808

If nothing helps, license owner may always contact SWSoft (NB! license owner,meaning purchased from SWsoft directly) and request to resend the updated license for installation:

https://register.swsoft.com/support/online_sales/form.php/

Hope that would be of any help

Regards,

 

[chep]

It's not that my port is not open and that the server cannot connect to swsoft. I ran the telnet, traceroute , etc just fine.

Are you saying that if someone upgrades from 8.2 to 8.3 they might end up with a situation where they have to provide a license key? It's not even a major version upgrade.

In addition to that are you saying that there is no way to downgrade back to 8.2 now?

Also, it seems really poorly designed (kind of like a scam) that someone would design it so that a user ends up in this situation. Here I have all this time and effort invested in my server and website and then I might accidentally upgrade to a minor version of Plesk from 8.2 to 8.3 and then get shut out of my own server. That seems real jacked. Would love to hear more information.

 

[simtech@]

I'm in the same boat... my server is just a week old and I just did an update to 8.3 and now I'm running into the same problem:

Downloading the file PSA_8.3.0/plesk_getkeyinfo.sh: 100% done.
Exchanging information with licensing server.base
Ask KA server for key update: product=PleskLogin current key number=PLSK<deleted by me> to version=1.0.0
Warning: your license key for the base component cannot be upgraded.
ERROR: Failed to check whether a new license key is available.
The installation will not continue.
Not all packages were installed.
Please, contact product technical support.

Using a VPS from godaddy, their tech support say it's not their problem. Though other folks told me the following:
"GoDaddy VPS have a jacked up partition structure!! Most likely out of room."