A service hangs, memory climbs, or a deploy leaves something in a bad state — and the fix is almost always the same one command: restart the service. Here's why that still usually means opening an SSH session, and how to skip it.

Why does restarting a service normally require SSH?

Because most monitoring tools stop at telling you something's wrong. The actual fix (systemctl restart nginx, or the Windows Services equivalent) has to happen on the box itself, so you open a terminal, authenticate, and run the command by hand — every single time, even though it's the same three steps as last time.

Can I restart a service remotely without SSH access?

Yes, if your monitoring tool supports whitelisted remote actions rather than just alerting. The key distinction is whitelisted: a tool that lets you run arbitrary shell commands remotely is a security liability, not a convenience feature. A tool that offers a small, fixed set of safe operations — restart a named service, kill a specific process, reboot — is a genuinely different (and safer) thing.

How MonitorFree handles it

Every server's Actions tab has exactly four remote operations: restart a service, kill a process, tail a log, and reboot. Nothing else runs. Each one is confirm-gated in the UI — a single click opens a confirmation state, a second click actually executes it — and every request and its result is written to that server's audit log, so you always know who ran what and when.

The actual flow

  1. Open the server's Actions tab
  2. Pick "Restart service," type the service name (e.g. nginx)
  3. Confirm — the agent picks up the request, runs it, and reports back
  4. Check the result inline, or in the audit log later

No SSH client, no saved connection profile, no typing the same restart command from memory at 2am. If you do want the real shell for something the whitelist doesn't cover, a full terminal and SFTP browser is one tab over in the same dashboard.

Try whitelisted remote actions free — up to 2 servers, no card required.

Start free

Frequently asked questions

Is it safe to restart services from a web dashboard?

It's as safe as the whitelist behind it. MonitorFree limits remote actions to four specific, confirm-gated operations rather than arbitrary command execution, and logs every request to an audit trail.

Does this work on Windows servers too?

Yes — the same whitelisted actions (restart a service, kill a process, tail a log, reboot) work through the native Windows agent as well as the Linux one.

What if the agent can't reach the server?

The action request times out after the agent fails to respond, and you'll see a clear failure message rather than a silent hang or a false success.