Server management
The screens that look after the machine itself — users, firewall, Fail2ban, cron, services, logs, runtimes and disk space.
Everything under Server in the sidebar is about the machine rather than any one application. Applications come and go; these screens are the ones you come back to when something needs looking after — a new deploy account, a port that has to be open, a scheduled command, a service that stopped, a disk filling up.
OSS Panel drives the ordinary Linux tools underneath: useradd, ufw,
fail2ban, the user crontab, systemd, the log files in /var/log, and the
PHP and Node.js packages. Nothing here is a private format — if you log in over
SSH afterwards, you will find exactly what the panel said it did.
What's here
System users
The Linux accounts that own your applications — create them, set shells, sudo, SSH keys.
Firewall
Which ports the internet can reach, as quick tiles or rules you write yourself.
Fail2ban
Jails, ban rules, the never-ban list, and banning or unbanning an address by hand.
Cron jobs
Schedule commands, pick who they run as, and read the output they captured.
Services
Start, stop, restart and enable the units the panel installed.
System logs
Every readable log on the box in one reader, with live tail, filters and download.
PHP
Install versions, switch extensions on and off, and edit php.ini safely.
Node.js
Install Node versions through fnm, set the default, and update npm.
Docker
Shared networks and volumes — on servers that host containers.
Disk cleaner
See what can safely be freed, clean it, and schedule it to happen on its own.
A note on permissions
Every screen in this section is gated by a role permission with its own Manage level. Where you only have read access, the page still loads and shows you the state — the buttons are the part that disappears, with a line saying which permission to ask an administrator for.