- General
-
Bugs
0
Not a bug
Ajenti Down After Update?
I updated Ajenti via the Ajenti package manager and it never came back after it displayed "Lost Connection".
It's been over 1/2 hour and I still can't access the Ajenti control panel. When I check services ajenti shows that it is running and so is a new service ajenti.dpkg-new
It's been over 1/2 hour and I still can't access the Ajenti control panel. When I check services ajenti shows that it is running and so is a new service ajenti.dpkg-new
Answer
0
Answer
Not a bug
Eugene Pankov (Project coordinator) 11 years ago
This can happen if ajenti package was installed with dpkg --force-all
I updated the rest of the packages on my VPS manually and now:
- the ajenti.dpkg-new service is gone.
- ajenti status looks correct.
- I get an ERR_SSL_PROTOCOL_ERROR when trying to connect to Ajenti on port 8000 via https.
- I cannot log in to Ajenti on port 8000 via http (I'm promoted for username & password but the login is rejected).
- the ajenti.dpkg-new service is gone.
- ajenti status looks correct.
- I get an ERR_SSL_PROTOCOL_ERROR when trying to connect to Ajenti on port 8000 via https.
- I cannot log in to Ajenti on port 8000 via http (I'm promoted for username & password but the login is rejected).
Here is what appears to have happened: the update renamed my config.json file and installed a new default config.json file.
I renamed my original file back to config.json and copied the installation_id value from the newly config.json file. It appears that everything is OK now.
Any idea as to why the update would disregard my config file?
I renamed my original file back to config.json and copied the installation_id value from the newly config.json file. It appears that everything is OK now.
Any idea as to why the update would disregard my config file?
Answer
Not a bug
This can happen if ajenti package was installed with dpkg --force-all
Customer support service by UserEcho
