System Monitoring¶
The system page provides a comprehensive overview of server resources, services and system tools.
Overview¶
The system page is divided into the following sections:
- Metrics — CPU, RAM, disks, load average
- Services — Status of all managed system services
- fail2ban — Intrusion detection status
- OPcache — PHP OPcache status per PHP version
- Server Reboot — Controlled server restart
Server Selection¶
In multi-server configurations, use the server selector to choose which server you want to monitor.
System Metrics¶
CPU¶
| Metric | Description |
|---|---|
| Usage | Current CPU usage in percent |
| Cores | Number of CPU cores |
Color coding:
- Green (< 70%) — Normal operation
- Yellow (70-90%) — Elevated load
- Red (> 90%) — Critical
Memory¶
| Metric | Description |
|---|---|
| Total | Total available RAM |
| Used | Currently used RAM |
| Free | Available RAM |
| Buffers | Buffer memory |
| Cache | File cache |
| Usage | Percentage usage |
Linux Memory Management
Linux actively uses free RAM as cache. High RAM usage is normal as long as sufficient free + cached memory is available.
Disks¶
The following is displayed per mount point:
| Metric | Description |
|---|---|
| Device | Block device (e.g. /dev/sda1) |
| Mount Point | Mount point (e.g. /, /home) |
| Total | Total capacity |
| Used | Used space |
| Free | Available space |
| Usage | Percentage usage |
Disk Full
At 90% usage, you should free up disk space. A full disk can lead to service outages and data loss.
Load Average¶
| Metric | Description |
|---|---|
| Load 1 | Average load over the last minute |
| Load 5 | Average load over the last 5 minutes |
| Load 15 | Average load over the last 15 minutes |
Load Interpretation
The load should ideally be below the number of CPU cores. A server with 4 cores and a load of 4.0 is fully utilized.
Uptime¶
The current operating time of the server since the last reboot.
Service Management¶
The services table shows all managed system services:
| Column | Description |
|---|---|
| Service | Name of the systemd service |
| Status | active, inactive, failed |
| Sub-State | Detailed status (e.g. running, dead) |
Service Actions¶
| Action | Description |
|---|---|
| Restart | Restart the service (systemctl restart) |
| Stop | Stop the service (systemctl stop) |
| Start | Start a stopped service (systemctl start) |
Monitored Services¶
| Service | Function |
|---|---|
| nginx | Web server |
| mariadb | Database server |
| postfix | Mail Transfer Agent |
| dovecot | IMAP/POP3 server |
| pdns | Authoritative DNS server |
| php8.x-fpm | PHP-FPM (per installed version) |
| rspamd | Spam filter |
| redis-server | Cache server |
| fail2ban | Intrusion prevention |
| proftpd | FTP server |
| unbound | DNS resolver |
fail2ban Status¶
Detailed fail2ban information:
Jails¶
| Jail | Monitors |
|---|---|
| sshd | SSH logins |
| postfix | SMTP authentication |
| postfix-sasl | SMTP SASL authentication |
| dovecot | IMAP/POP3 logins |
| nginx-http-auth | Nginx HTTP authentication |
| roundcube-auth | Roundcube webmail logins |
| recidive | Repeat offenders (all jails) |
Banned IPs¶
The following is displayed per jail:
- Total Bans — Historical total count
- Currently Banned — List of currently banned IP addresses
Unban IP¶
- Select the jail
- Click Unban next to the IP address
- The IP is released immediately
fail2ban Jail Configuration¶
Jail parameters can be configured directly in the panel without manually editing configuration files.
Adjust Configuration¶
- Navigate to System > fail2ban Status
- Scroll to Jail Configuration
- Adjust the desired parameters:
| Parameter | Description | Default |
|---|---|---|
| Enabled | Enable/disable jail | Varies per jail |
| Max. Retries | Number of failed attempts before ban | 5 |
| Ban Time (s) | Duration of ban in seconds (−1 = permanent) | 600 |
| Find Time (s) | Observation window in seconds | 600 |
- Click Save on the respective jail
Changes are immediately written to /etc/fail2ban/jail.d/netcell-panel.conf and fail2ban is automatically reloaded.
Hardening Recommendations
- sshd: Max 3 attempts, 3600s ban time
- postfix/dovecot: Max 5 attempts, 600s ban time
- recidive: Enable for repeat offenders (permanent ban)
OPcache Status¶
OPcache accelerates PHP by caching compiled bytecode in memory.
Status per PHP Version¶
For each installed PHP version (8.1, 8.2, 8.3, 8.4) the following is displayed:
| Metric | Description |
|---|---|
| Enabled | OPcache on/off |
| Memory Used | Used OPcache memory |
| Memory Free | Available OPcache memory |
| Wasted | Unusable memory (fragmentation) |
| Wasted (%) | Percentage of wasted memory |
| Cached Scripts | Number of cached PHP files |
| Cache Hits | Successful cache hits |
| Cache Misses | Cache misses |
| Hit Rate | Hit rate in percent |
Flush OPcache¶
- Select the PHP version
- Click Flush OPcache
- All cached scripts are discarded
When to flush OPcache?
Flush the OPcache after PHP updates or when changes to PHP files are not immediately visible.
Server Reboot¶
Downtime
A server reboot interrupts all running services. Schedule reboots outside of peak usage hours.
- Click Reboot Server
- Confirm the reboot in the confirmation dialog
- The server is gracefully shut down and restarted
- All systemd services start automatically
Reboot Required
If a kernel update has been installed, the dashboard displays a "Reboot required" notice.