| Help! Kloxo Control Panel "Gone"! [message #97619] |
Sat, 14 April 2012 14:52  |
|
Hello,
I have been using Kloxo on a VPSville host-in-a-box account for a couple of years now (mostly basic stuff -- setting a couple of websites for myself, adding email addresses). I am quite a newbie and don't really know how to perform any server operations without Kloxo.
Today I noticed that my version of Kloxo was a bit out of date (6.1.6), so I used the standard update option from within Kloxo to do an update (supposedly to 6.1.12), just like I've done quite a few times before. This time something must have gone wrong (don't know what - eveything seemed OK) since now I no longer have access to Kloxo. It's been a couple of hours now. I have also tried rebooting the server (after more than an hour) but it didn't help.
https:
//<IP>:7777/login/
returns a blank page (or rarely an internal server error message).
My websites are still on and seem to be OK. I can still access them via HTTP and FTP, so my websites' visitors are not affected, but I don't know how perform any server operation (e.g. add email address) without Kloxo.
Is there a way to regain the control panel without losing all my server settings and without significantly disrupting my websites?
Any help would be most appreciated.
Ta,
Raphael
|
|
|
| Re: Help! Kloxo Control Panel "Gone"! [message #97621 is a reply to message #97619] |
Sat, 14 April 2012 15:55   |
|
UPDATE:
After three hours during which I had no control panel, Kloxo suddenly returned from the dead (and updated to version 6.1.12)!
I don't know if the problem was just that the update took three hours (is it likely?) and I was too impatient, but anyhow am I glad to see it!!!
Issue closed.
|
|
|
| Re: Help! Kloxo Control Panel "Gone"! [message #97623 is a reply to message #97621] |
Sat, 14 April 2012 16:10  |
|
UPDATE #2:
Before posting here, I had opened a ticket with VPSville. After they had said that I should look for a solution by myself, I posted here.
VPSville now updated me that it was them that resolved the issue (it had not, as I had assumed, spontaneously resovled itself).
Their terse message reads: "Kloxo had a package conflict which had to be resolved from the command line. Its been updated and should be working again for you now."
|
|
|