UnderHost
Knowledgebase Docs

How to safely reboot your VPS or dedicated server

When and how to reboot your Linux server-safe reboots, forced reboots via CustomerPanel, what happens during reboot, and what to check afterwards.

On this page

Rebooting a server restarts all services and applies kernel updates. It briefly takes your site offline, so plan it appropriately. Most reboots complete in 60–120 seconds.

When to reboot

  • After applying Linux kernel updates (required for the new kernel to take effect)
  • When a service (MySQL, Nginx, PHP-FPM) fails to restart normally
  • After major system configuration changes
  • When the server is in an inconsistent state and SSH is still accessible
  • As a last resort when the server is unresponsive (use CustomerPanel force-reboot)

Safe reboot via SSH

A graceful reboot sends shutdown signals to all processes before restarting. This is always preferred when SSH is accessible:

# Reboot immediately
reboot

# Schedule reboot in 5 minutes (gives time to notify users)
shutdown -r +5 "Server will reboot in 5 minutes for maintenance"

# Cancel a scheduled shutdown
shutdown -c

After issuing the reboot command, your SSH connection will drop within a few seconds. Wait 60–120 seconds, then attempt to reconnect.

Reboot via CustomerPanel

  1. Log in to customerpanel.ca
  2. Go to Services → My Services → your VPS
  3. Click Reboot
  4. Confirm the action

The CustomerPanel reboot sends a graceful shutdown signal first. If the server is completely unresponsive, use Force Reboot (equivalent to holding the power button-processes are killed immediately without clean shutdown).

Force reboot can cause filesystem issues

Force rebooting is like pulling the power cord. It can leave databases in an inconsistent state or cause filesystem corruption. Use it only when the server is completely unresponsive to a normal reboot.

What to check after reboot

  1. SSH back in and verify the server is up
  2. Check that all services are running: systemctl status nginx php8.2-fpm mysql
  3. Visit your website to confirm it loads correctly
  4. Check error logs for anything that failed to start: journalctl -xe

Services set to enabled in systemctl start automatically at boot. If a service is not starting automatically, run systemctl enable servicename to enable it.

Was this article helpful?

Need a safe server reboot?

Our NOC team can perform planned reboots with minimal downtime during maintenance windows.

Related articles

Back to Server Management