SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor · Updated 2026-10-22

Cockpit or Webmin: Which One Better for Ubuntu VPS?

Cockpit or Webmin for Ubuntu VPS? See wetin each panel fit change, how login works, why public ports dey risky, and when SSH plus Ansible better.

Cockpit vs Webmin: di short answer

Cockpit and Webmin na both web panels wey you fit use manage Linux server from browser, but dem dey answer different questions. Cockpit dey come inside your distribution own repository, and e dey read the machine through systemd, journald, polkit and udisks. So e dey show you server wey you still dey manage through SSH. Webmin old pass and e cover more things: e dey write configuration files for Apache, BIND, Postfix, MariaDB and plenty other services wey Cockpit no dey touch. E dey also run im own web server as root to do that work.

Install Cockpit when you want live view of one box, log reader, and emergency terminal. Install Webmin when you need form-based editor for service wey you no want configure by hand. No put any of dem for public port with password login. If you already dey run more than two or three servers, the honest answer often na neither. SSH plus Ansible path dey scale better than any panel.

Wetín each panel fit actually change

Cockpit base install small, and most areas na separate packages wey you fit leave out:

  • systemd services and timers: start, stop, enable, and read the unit file
  • the journal, filtered by unit and priority, wey be journalctl with date picker
  • local accounts, group membership, and authorized SSH keys
  • storage with cockpit-storaged: partitions, LVM volume groups, filesystems and mount points
  • containers with cockpit-podman, wey dey manage Podman only
  • package updates with cockpit-packagekit
  • graphs of CPU, memory, disk and network with cockpit-pcp
  • root terminal for browser tab

Two areas dey look broken for Ubuntu VPS, but dem no be broken. Cockpit Networking page na front end for NetworkManager, while Ubuntu server images dey use netplan with systemd-networkd, so the page dey missing or empty. No install NetworkManager for remote box just to bring am back, because e go take over the interface, and one mistake there fit also cost you the SSH session. Cockpit firewall controls na front end for firewalld, while Ubuntu dey use ufw, so you no go get any firewall controls at all. You go continue to run sudo ufw status for terminal.

Webmin cover much more area, because e na collection of per-service modules instead of one program:

  • Apache, nginx, BIND, Postfix, Dovecot, MariaDB, PostgreSQL and Samba configuration through forms
  • users, groups and disk quotas
  • cron jobs and system clock
  • package updates, plus file manager wey fit upload and download
  • firewall front ends, including one for iptables and one for firewalld
  • configuration file backups, and cluster modules wey push one change go other Webmin servers

Most Webmin forms dey edit the real files under /etc, with no hidden database behind dem. So if /etc dey inside version control, sudo git -C /etc diff after you save form go show wetin the module write there. E no go show actions wey run command or execute SQL, like the MariaDB and PostgreSQL modules dey do, or writes to files outside /etc. Within these limits, na the fastest way to learn wetin Webmin page really dey do. The Webmin install and first login walkthrough go explain the module tree in detail. Virtualmin and Usermin na separate products wey build on the same engine, for shared hosting and end users, and dem inherit everything wey we talk here about exposure.

How each one dey authenticate

Cockpit no get user database. Its login page dey run PAM (pluggable authentication modules) stack for /etc/pam.d/cockpit, so the accounts na your Unix accounts and the passwords na your Unix passwords. By default, e no dey allow root because /etc/cockpit/disallowed-users list am. Privileged actions dey pass through polkit, and the interface dey ask for your password again before e change anything. Na why the page header fit show "Limited access" until you escalate.

This design get one result wey people dey see for hardened box. If you follow key-only SSH login with password authentication disabled, the account fit no get any usable password, so Cockpit login go reject am while ssh still dey work. Check am for the server:

sudo passwd -S deploy

Output wey start with deploy L mean say the password dey locked, so PAM no get anything to accept and no password wey you type fit work. P mean say usable password dey set. Cockpit own login page no dey accept SSH keys. E only use keys when Cockpit connect from the machine wey you log into go another host.

Webmin dey keep its own users for /etc/webmin/miniserv.users, separate from /etc/passwd, and you fit also configure am to authenticate against Unix accounts. Webmin user wey get all modules na root for that machine, no matter wetin their login shell talk. Webmin release its own TOTP (time-based one-time password) support and its own host blocking after repeated failed logins. You switch both on inside Webmin Configuration. Cockpit go get second factor only if you add one to PAM, for example with libpam-google-authenticator.

How each one dey update

Your distribution dey package Cockpit. For Ubuntu 24.04, e dey come from the archive, and the upstream project recommend the backports pocket if you want newer build:

. /etc/os-release
sudo apt update
sudo apt install -t ${VERSION_CODENAME}-backports cockpit
sudo systemctl status cockpit.socket
apt policy cockpit

apt policy cockpit dey print the version wey you install and the repository wey e come from. If you run am without package name, apt policy go list only the priority of each source. If backports no get newer build, apt go fall back to the archive version, and that one dey okay. cockpit.socket suppose read active (listening). Security fixes go then arrive through the same unattended-upgrades run wey your kernel dey use, from publisher wey you already trust.

Webmin no dey inside Ubuntu archive. The official install first add Webmin own repository and signing key:

curl -o webmin-setup-repo.sh https://raw.githubusercontent.com/webmin/webmin/master/webmin-setup-repo.sh
sudo sh webmin-setup-repo.sh
sudo apt-get install webmin --install-recommends

Read that script before you run am, because e dey run as root. From that point, every apt upgrade for the server go also pull packages from Webmin repository. So you don add second publisher wey get root-level trust for the system. Na this be the real cost of Webmin, and e deserve plain example: CVE-2019-15107 na backdoor inside several 1.9x packages wey give unauthenticated command execution. Users receive am because the project build host get breached, not because the source repository get breached. Distribution packaging no make this impossible. But e add build and review step wey you no need maintain by yourself.

Why none of dem suppose dey for public port

Cockpit dey listen on TCP 9090 and Webmin dey listen on TCP 10000. Both dey use TLS (transport layer security) with self-signed certificate, so the first thing wey you go see na browser warning. How to create and trust self-signed certificate explain wetin that warning tell you and wetin e no tell you. Dem dey scan both ports all the time, and both panels lead to root, so guessed or reused password fit compromise the whole server.

The safe pattern na to bind the panel to localhost and reach am through SSH tunnel. For Cockpit, override the socket unit:

sudo systemctl edit cockpit.socket
[Socket]
ListenStream=
ListenStream=127.0.0.1:9090

The empty ListenStream= for im own line dey required. systemd dey append to list settings, so if you no put am, the unit go keep the original 0.0.0.0:9090 and add the new address. Your panel go still dey public. Apply the override and check wetin dey listen:

sudo systemctl daemon-reload
sudo systemctl restart cockpit.socket
sudo ss -lntp | grep 9090

The output suppose show 127.0.0.1:9090. Address of *:9090 or 0.0.0.0:9090 mean say the override no take effect. Now open the tunnel from your own machine and browse to https://localhost:9090:

ssh -N -L 9090:127.0.0.1:9090 deploy@203.0.113.10

The local port no need match the remote one. Cockpit dey build the origin wey e expect from the Host header wey browser send. So tunnel from local port 9999 wey you open at https://localhost:9999 go pass the same check, because the browser's Host and Origin headers name the same address. The check go fail when something between browser and Cockpit change Host, like reverse proxy wey no pass the original header through. The login page go load, but login go fail, and cockpit-ws go log received request from bad Origin. That line dey inside the journal of the cockpit-wsinstance-https@ units, no be cockpit.service, so read am with sudo journalctl -u 'cockpit-wsinstance-https@*'. To accept public address wey different from wetin Cockpit dey see, name am for /etc/cockpit/cockpit.conf:

[WebService]
Origins = https://panel.example.com

Restart with sudo systemctl restart cockpit make e pick am up. For Webmin, the equivalent setting dey for /etc/webmin/miniserv.conf:

bind=127.0.0.1
sudo systemctl restart webmin
sudo ss -lntp | grep 10000
ssh -N -L 10000:127.0.0.1:10000 deploy@203.0.113.10

Webmin still dey check Referer header for form posts and dey refuse requests wey look like say dem come from another host. Na this one dey break first attempt at reverse proxy. The referers= line for /etc/webmin/config na where you allow the proxy hostname, and webprefix= for that same file na where you tell Webmin say e dey under one path.

Authenticated reverse proxy na the other option: nginx for front, with an Authentik single sign-on layer wey dey handle login. E dey work, but e na second-best option. The panel still dey run as root behind the proxy, and now you dey maintain two front doors instead of one. Tunnel no add any listening service to internet at all, and e reuse the SSH key wey you already protect.

Which panel you fit use for box wey already dey run production services

Cockpit, because of two reasons wey matter when other people dey depend on the machine. E dey use socket activation, so cockpit-ws dey run only while session dey open, and no permanent root daemon dey wait for port. E no own anything: if you remove the package, every service go continue to run exactly as before, because Cockpit no store any configuration of its own. Webmin's miniserv.pl dey remain resident whether anybody log in or not. Check wetin your own dey cost with systemctl status webmin; e go print resident memory of the running process.

If you need Webmin's DNS or mail modules, give dem server of their own. Webmin box wey dey do one job and bind to 127.0.0.1 na contained risk. Webmin wey share host with application wey your customers dey use no be. Do the basic setup before you install either panel: the first ten minutes for new VPS cover the non-root user and firewall wey both panels assume say e dey already there.

When the answer no be either

A panel dey for each server and na manual work, plus e no keep record of wetin change or why. This one fit okay for one box. For five boxes, you go dey repeat yourself. For twenty, you go dey guess which server miss the change. Cockpit fit add other hosts to one session through SSH, but that host switcher don deprecated since Cockpit 322. Its default now depend on the distribution. Where e dey off, you need AllowMultiHost=yes for /etc/cockpit/cockpit.conf. Even when you enable am, you still go click the same change five times.

The alternative na plain SSH with your configuration inside a git repository. Manage several Linux servers from one place explain the structure of that setup. a first Ansible playbook apply the same firewall rule to every host from one file wey you fit review as a diff. Container work follow the same pattern: docker compose up -d through SSH from a file for git, as shown for the Docker Compose basics guide, better pass clicking through any panel. Besides, Cockpit no manage Docker at all.

Use panel for things wey terminal no good at, like reading a metrics graph or finding which one among forty units fail. Use code for anything wey you go do more than twice.

Failure modes and the strings wey you go see

Cockpit dey reject password wey SSH dey accept. The account na key-only. sudo passwd -S alice dey print L for the second field, so PAM no get password to check. Set one with sudo passwd alice, or continue to use that account for SSH and log in to Cockpit with another user.

Cockpit dey refuse root even when the password correct. /etc/cockpit/disallowed-users dey list root. Log in as normal user wey get sudo rights. Na the intended way be this, because polkit go record which person escalate.

Cockpit no show Networking or Firewall page. Those pages need NetworkManager and firewalld. Ubuntu VPS dey run netplan with systemd-networkd and ufw, so the pages no go appear. Nothing spoil, and the fix na to continue using ufw over SSH.

Cockpit login page load behind proxy, then login fail. The proxy change the Host header, so Origin check fail and sudo journalctl -u 'cockpit-wsinstance-https@*' show received request from bad Origin. Pass the original Host through, or set Origins for /etc/cockpit/cockpit.conf. Plain SSH tunnel no cause this, no matter which local port you choose.

Webmin form posts dey fail after you put am behind proxy. The Referer check dey reject dem. Add the proxy hostname to referers= for /etc/webmin/config, and set webprefix= for that file when the panel dey serve under a path.

You no sure whether panel dey exposed. sudo ss -lntp | grep -E '9090|10000' go answer that from the server itself, and Webmin dey write every login attempt to /var/webmin/miniserv.log. E worth reading am once after any change to how e dey listen.

FAQ

Cockpit or Webmin better for one Ubuntu VPS?

For most people, Cockpit better, because e dey come from Ubuntu own repository, system patches dey update am together with the rest of the system, and e dey run only when browser session open. Choose Webmin when you need form-based editor for service wey Cockpit no dey support, like BIND or Postfix. But accept say Webmin web server go run as root all the time, and Webmin own repository go provide the updates.

I fit run Cockpit and Webmin for the same server?

Yes. Dem dey use different ports, 9090 and 10000, and dem no conflict because each one dey edit the system directly instead of owning am. E still no be good trade-off. Each panel na separate root-capable login for the same machine, so you double the exposure just to save few clicks. If you install both, bind both to 127.0.0.1 and reach dem through SSH tunnel.

E safe to open port 9090 or 10000 to internet?

Password login no make am safe. Both panels lead to root, and routine scanning fit find both ports within hours after you open dem. Bind the panel to 127.0.0.1, then run ssh -N -L 9090:127.0.0.1:9090 user@host and browse go https://localhost:9090. Confirm with sudo ss -lntp | grep 9090. E must show 127.0.0.1:9090 instead of 0.0.0.0:9090. Authenticated reverse proxy na acceptable second option.

Why my Cockpit login dey fail when SSH with key dey work?

Cockpit dey authenticate through PAM with Unix password, and e login page no accept SSH keys. For hardened server, the account often no get usable password. Run sudo passwd -S youruser. An L for the second field mean say the password lock, so PAM get nothing to accept and every attempt dey reject. Set password with sudo passwd youruser, or use different account for the panel.

Cockpit dey manage Docker containers?

No. Cockpit container page dey come from cockpit-podman and e dey manage Podman. Dem drop the old Docker module years ago, and dem no dey bring am back. If your services dey run under Docker, manage dem with compose file for version control through SSH. Make Cockpit handle the system around dem, like the journal and disks.

Dis article help you?

#cockpit#webmin#server-management#admin-panel#ubuntu