Since your VPS is self-managed, all system configuration — including which services start automatically — is your responsibility.
A very common issue is that after a reboot:
SSH stops working
Your website goes offline
Other services (databases, panels, etc.) don’t start
This usually happens because the services were installed but not enabled to start on boot.
What’s Happening Technically
Most modern VPS distributions use systemd to manage services.
There are two separate actions when working with services:
Start a service now
sudo systemctl start ssh
Enable a service to start automatically on boot
sudo systemctl enable ssh
If you only start a service but don’t enable it, it will stop working after a reboot. If you do not do this for the SSH service, after reboot, you will not be able to access the server via SSH, and you will need to access the server via Emergency Console/ VNC and activate SSH service.
Commonly Affected Services
Make sure you enable all critical services, such as:
SSH (remote access)
Web server (e.g. Nginx or Apache HTTP Server)
Database (e.g. MySQL / MariaDB)
Control panels (if used)
How to Fix the Issue
1. Enable SSH to Start on Boot
Depending on your system, the service name may differ:
sudo systemctl enable ssh
or
sudo systemctl enable sshd
Then start it:
sudo systemctl start ssh
2. Enable Your Web Server
For Nginx:
sudo systemctl enable nginx
sudo systemctl start nginx
For Apache:
sudo systemctl enable apache2
sudo systemctl start apache2
3. Verify Enabled Services
To check if a service is enabled:
systemctl is-enabled ssh
Expected output:
enabled
4. Test Before Logging Out
Always verify before closing your session:
sudo reboot
Then reconnect via SSH to confirm everything works.
If You’re Already Locked Out
If SSH is not running after reboot, you will need to use:
Restore the backup if you have the backup component for your VPS
From there, you can log in and enable the services as shown above.
Important Responsibility Note
For self-managed VPS services:
The provider ensures the server is online and accessible
Configuration inside the OS is client's responsibility
Issues like services not starting after reboot are configuration-related, not infrastructure failures.