09-07-2019, 01:45 PM
@rudra @"Hidden Refuge"
Ops, my bad. I wrote all the steps needed starting from OpenVZ deployment because on my investigation I had to start from scratch building up my test environment. I can say that using OpenVZ is REALLY EASY.
The commands "vzctl enter <ID> && passwd root" were need because after creating and starting the OpenVZ container I couldn't know what password was set by who created the template. I HAD to set a password for the root user to be able to SSH into the newly created machine. But, if you get a OpenVZ-based VPS from POST4VPS or anywhere you will have already the credentials to login via SSH. So these commands can be skipped.
I will rewrite the steps to be more clear and removing the OpenVZ reference.
I have succeed to obtain a VPS surviving the reboot on my testing environment with BASIC OpenVZ settings. It could be nice if some staff could test it on a spare/unused VPS to check if "Enterprise" Settigns are compatible with this "workaround"
Ops, my bad. I wrote all the steps needed starting from OpenVZ deployment because on my investigation I had to start from scratch building up my test environment. I can say that using OpenVZ is REALLY EASY.
The commands "vzctl enter <ID> && passwd root" were need because after creating and starting the OpenVZ container I couldn't know what password was set by who created the template. I HAD to set a password for the root user to be able to SSH into the newly created machine. But, if you get a OpenVZ-based VPS from POST4VPS or anywhere you will have already the credentials to login via SSH. So these commands can be skipped.
I will rewrite the steps to be more clear and removing the OpenVZ reference.
Hidden Refuge Wrote:So my point stands. If you break the network by installing a network manager (either on purpose or by accident through other packages) and you don't have control panel access: only staff can fix the issue by applying simple commands to either stop, disable or remove the network manager. If you have control panel access you can fix it yourself using the emergency SSH access that is provided in the control panel.This "workaround" prevents you to break network settings, so you will not need to ask to the staff to fix it. NetworkManager will be activated on the next reboot, but if you uninstall it first the problem will never show up.
I have succeed to obtain a VPS surviving the reboot on my testing environment with BASIC OpenVZ settings. It could be nice if some staff could test it on a spare/unused VPS to check if "Enterprise" Settigns are compatible with this "workaround"