The problem
When httpd, mysql or exim dies — OOM-killer, failed reload, full disk — every site on the server goes down with it. Customers notice immediately; you find out from their emails in the morning. External uptime pingers tell you a site is down, but not which service died, and fixing it still means finding a laptop and opening SSH.
The solution
VpsMonitor.Pro probes the critical services — web server, MySQL, Exim, crond, named — every 60 seconds over its SSH connection. When one stops, a Telegram alert reaches your phone within about two minutes, naming the exact service and how long it has been down. No third-party pinger, no guessing which layer failed.
Recovery is in the same window: the Services view shows each service’s live status with a Restart button — one confirmation and systemctl restart runs over SSH, handling the unit-name differences between distributions (and restarting every PHP-FPM version pool at once when needed). For the rare hard case there is a double-confirmed full VPS reboot.
The same view’s checks also catch the quieter failures: a service that is “up” but failing — Apache serving errors, mail queue jammed — through the scheduled graded checks.
Frequently asked questions
How fast will I know a service died?
The watch probes every 60 seconds and alerts once a service has been down for two minutes — fast enough to often fix things before the first customer email.
Is restarting from the app safe?
It runs the same systemctl restart you would type, against a fixed whitelist of services, with confirmation first. Nothing custom, nothing destructive.
What usually kills MySQL at night?
The Linux OOM-killer during a memory spike, or a full disk. The memory chart and disk checks in the same app usually show the cause right next to the alert.
Get a license · Download free — 7-day trial