Procédure
On a managed VPS, LWS maintains the server: updates, security, and configuration. You manage your sites, e-mail addresses, and databases from the ISPConfig or HestiaCP panel, without root access. If you have enabled root access, or if you have a KVM VPS, you administer the server yourself: updates and security are your responsibility. In all cases, LWS takes care of the physical server and the network.
An LWS VPS Server works in one of two modes: managed or SSH root access. The KVM VPS is another offer, always with root access.
| Who takes care of it? | Managed VPS | VPS with root access | KVM VPS |
|---|---|---|---|
| SSH root access | No (user SSH access and web console) | Yes | Yes |
| ISPConfig or HestiaCP control panel | Included | Not provided (an already installed ISPConfig is no longer updated by LWS) | Not provided |
| System and server software updates, including security patches | LWS | You | You |
| Server maintenance and configuration | LWS | You | You |
| Your sites, e-mail addresses, and databases | You, from the panel | You | You |
| 1 hour of managed service included per month | Yes | No | No |
| Physical server, network, and anti-DDoS protection | LWS | LWS | LWS |
| Restart or reinstall the VPS from the customer area | You | You | You |
LWS technicians handle maintenance, updates, and configuration of your VPS. Automatic updates apply only in managed mode. For example, when a security flaw affects PHP, our teams apply the patch: you do not need to do anything.
You do not have root access. You manage your hosting from the control panel chosen at order time (ISPConfig or HestiaCP): sites, e-mail addresses, databases. One hour of managed service per month is included for intervention requests on the server.
Root access and managed service are mutually exclusive: disabling managed service gives you root access, and your VPS is no longer managed. You then administer your server alone, with a web console and the ability to enable a VPN. Disabling is done from your customer area, as explained in the help article How do I enable ROOT SSH on my managed ISPConfig dedicated server by LWS?.
From that point on, system updates, PHP and panel updates, as well as server security, are your responsibility. LWS continues to manage the physical server hosting your VPS and its network.
The KVM VPS has no managed offer: you are root from delivery and manage your server yourself. This autonomy requires some server administration knowledge, especially for updates and security. Technical support remains available to guide you.
If you prefer LWS to maintain your server, it is the VPS Server range, in managed mode, that offers this.
The presence of ISPConfig does not prove that your VPS is managed: a VPS switched to root access keeps its ISPConfig, but LWS no longer updates it.
If in doubt, open a ticket from your customer area (Support, then Contact support) and indicate your server reference (VPS-…): support can see whether your VPS is managed by LWS.
Reply to the relevant ticket, or open one, indicating your VPS reference and the mode you believe you have. Support checks the mode recorded for your server and confirms who must perform the operation.
You can request a one-off paid intervention from a technician: see Managed Dedicated VPS Server. For regular follow-up, paid service levels are presented in Support options for dedicated VPS server. Back up your server before any update.
No, even on a managed VPS: your data belongs to you. First check the space used by each site and each mailbox in ISPConfig, downloaded backups left in a site's backup folder, test sites that are no longer used, the trash, and webmail spam. For system-related matters, to which you do not have access, open a ticket: our teams will check with your consent. A plan with more disk space is also possible.
No. On Low Cost VPSs, support checks that the server is reachable and working, but does not help install applications or correct settings made on the server. Details are in Limits / quotas / Support for LowCost Dedicated VPS Servers.
The free managed service of a Private Cloud is limited to one VPS installed on it, with Debian and ISPConfig. To find out which of your VPSs benefits from it, open a ticket from your customer area.
Connect using an SSH key rather than a password: the procedure is in How to secure SSH access to an LWS VPS: keys only and fail2ban.
Ask the LWS team and the community. Answers are published after moderation.