The Services card on the server overview lists every service with its state, memory and when it started. Most can be restarted with one click.
| Service | Restart when | Effect of a restart |
|---|---|---|
| nginx | Rarely needed; settings changes reload it on their own. | Configuration is tested first; a bad one is never applied. |
| php8.x | The site is stuck or slow and PHP workers are busy. | Running requests end; OPcache is emptied. A few seconds. |
| mariadb | After a crash, or on our advice. | All sites lose the database for a few seconds; running queries fail. |
| redis / redis-sessions | Magento cache misbehaves. | Restarting the cache instance empties the cache. The sessions instance keeps carts on disk. |
| varnish | Pages look stale after changes, or Varnish stopped. | The page cache starts empty and fills again. |
| opensearch | Magento search returns errors. | Search is down for up to a minute. |
| postfix | Email is stuck in the queue. | Queued email is kept and sent again. |
| fail2ban, crond, clamd | On our advice. | No effect on visitors. |
Restarting is a quick fix, not a cure. If you need to restart the same service often, open a ticket so we can find the cause.
Inactive is not always bad
Varnish is only active when a Magento store uses it, and clamd only while a malware scan runs. An inactive (dead) state for those is normal.
Did this solve it? If not, tell us what you see and we look at your server.
Open a ticket