How to Use Cockpit: The Beginner's Guide to the Linux Server Dashboard

CodexFuse Team · 2026-11-01T10:09:49.089Z · 9 min read

How to use Cockpit, the Linux server web dashboard: install on Ubuntu and Fedora, first login, the full dashboard walkthrough, add-ons, and multi-server management.

What Is Cockpit?

Cockpit is a free, open-source web dashboard for managing a Linux server from your browser. Instead of memorizing command-line syntax, you click through real system tools — service controls, logs, storage, networking, user accounts, and software updates — and every action runs through the same OS interfaces the terminal uses, so the GUI and the command line stay in perfect sync. This cockpit tutorial covers the whole arc: install, first login, the full dashboard walkthrough, add-ons, and multi-server use on the current release.

If you rent a VPS or run a homelab box, learning how to use Cockpit is one of the fastest ways to get comfortable administering it. It is not a car or an airplane here — this is the Cockpit server dashboard, the Linux web dashboard maintained by the Cockpit project (latest release Cockpit 357, as of late October 2026). Pair it with our Docker beginner guide and you can run a container host entirely from a browser tab.

How Do You Install Cockpit on Ubuntu, Debian, Fedora, and Arch?

Installing Cockpit is one command on every major distro, followed by enabling its socket so the web service starts on demand. The official install page recommends your distro's backports repo on Debian/Ubuntu to get the newest release; Fedora Server even ships it by default.

After installing, start the service with sudo systemctl enable --now cockpit.socket. Cockpit is socket-activated: the web server launches when a browser connects and exits 90 seconds after the last logout, so it costs you nothing when idle.

Cockpit usually lives on a VPS you rent and administer yourself — if that concept is new, read what is VPS hosting first, then come back and install on your instance.

How Do You Open Cockpit on Port 9090 Safely?

Cockpit listens on port 9090 over HTTPS — browse to https://<your-server-ip>:9090 and plain HTTP redirects to HTTPS automatically. On Fedora/RHEL open the port with sudo firewall-cmd --add-service=cockpit --permanent, and on Ubuntu/Debian with sudo ufw allow 9090/tcp.

Expect a browser security warning on your first visit: Cockpit generates a self-signed certificate (/etc/cockpit/ws-certs.d/0-self-signed.cert) on first run, so the warning is normal — verify the address is really your server, then proceed. For anything beyond quick tests, add a real CA certificate.

Do not leave Cockpit's port 9090 open to the entire internet. Reach it over a VPN instead — our Tailscale beginner guide shows one way to do that — or put a reverse proxy with authentication in front of it.

How Do You Log In to Cockpit for the First Time?

You log in with your server's own system credentials — Cockpit uses PAM, so there is no separate Cockpit user database; use the same account you SSH with. Root login is blocked by default on most modern distros, so log in with a sudo-enabled user instead.

Non-root logins start in "Limited access" mode: a yellow banner on the Overview page and a "Limited access" indicator in the header, with read-only pages working and write actions disabled. Click the indicator and re-enter your own password to switch to administrative access — the session then has exactly the same privileges as an SSH login, and the toggle is remembered across visits.

What Does the Cockpit Dashboard Show You?

The Overview page is your landing pad: at-a-glance system health with CPU, memory, disk, and network graphs. From the left sidebar you get Logs (searchable system journal), Storage (disks, partitions, NFS, RAID, encryption), Networking (interfaces, IP addresses, traffic, bonds, bridges, VLANs, and firewall editing), Accounts (Unix users, groups, SSH keys), Services (systemd units), Software Updates, and a built-in Terminal.

One useful distinction: Cockpit changes your system's state — it is an administration dashboard. A dedicated monitor like our Netdata beginner guide covers the watch-only role; run both if you want deep metrics beside the controls.

How Do You Manage System Services and Read Logs?

The Services page lists every systemd unit with separate views for targets, system services, sockets, timers, and paths. Select any service to start, stop, restart, reload, or enable it at boot, and read its recent journal entries right on the same page — handy when a service misbehaves.

Timers created inside Cockpit run via /bin/sh and stay editable from the GUI. And because Cockpit drives the same APIs the terminal uses, anything you change in the web console appears instantly in the shell and vice versa — you can freely mix the two without one hiding state from the other.

Can You Use a Terminal Inside Cockpit?

Yes — the Terminal page is a real command-line session in your browser, authenticated as your logged-in user. It is the escape hatch for everything the GUI does not cover: you can run a package install, edit a config, or tail a log, and the dashboard reflects the change immediately.

This is what makes Cockpit a teaching tool as much as an admin tool. Perform an action in the GUI, then look at what it did in the terminal, and you gradually learn the underlying commands instead of staying dependent on the buttons.

How Do You Manage Users and Software Updates in Cockpit?

The Accounts page lets you create, update, and remove Unix user accounts and groups, and manage SSH authorized keys — including password and role settings per account. Everything maps to real system users, not a dashboard-specific roster.

Software updates run through the cockpit-packagekit add-on, which sees and applies updates on both RPM and DEB systems via PackageKit; OSTree-based systems use cockpit-ostree instead. The page shows available updates, lets you apply them, and can be set to check automatically.

Which Cockpit Add-ons Are Worth Installing?

Cockpit ships lean and grows through add-on packages, all listed on the project's official applications page. Install only what you need:

• cockpit-storaged — deeper storage management: local partitions, encryption, NFS, RAID, iSCSI
• cockpit-networkmanager — network interfaces plus firewall editing
• cockpit-packagekit — the Software Updates page, RPM and DEB
• cockpit-podman — download and manage containers (Podman is the Docker replacement in Cockpit's world)
• cockpit-machines — create and run virtual machines
• cockpit-files — a featureful file browser for everyday file sharing and file tasks

Do not install cockpit-pcp from an old guide — it is obsolete since Cockpit 326, when the bridge started implementing PCP metrics itself, so the performance graphs on the Overview page already come built in.

For containers, install cockpit-podman and work through our Podman beginner guide to learn the runtime behind the buttons.

How Do You Manage Multiple Servers With Cockpit?

The classic in-browser host switcher — top-left corner, add a host, hop between servers — is being deprecated. It is already disabled by default in Fedora 41+ and Debian Unstable/Testing because the project's JavaScript cannot be isolated across connected hosts, and the team intends to disable it entirely; on current stable distros (RHEL 9, Debian 12, Ubuntu 22.04/24.04) it still works and can be re-enabled via cockpit.conf.

The modern routes are the Cockpit Client flatpak, which manages multiple hosts over SSH without needing port 9090 on each remote, and the quay.io/cockpit/ws container, which connects even to machines without Cockpit installed ("package-less" sessions). Whichever route you pick, the remote hosts must be reachable over SSH with keys set up.

Cockpit vs Webmin: Which Should You Use?

Both are free web panels for Linux, but they take opposite approaches. Cockpit drives the OS's own APIs and tools, so terminal and GUI always agree; Webmin edits Unix configuration files directly and ships deep application modules.

Choose Cockpit for everyday server administration and learning the underlying system; choose Webmin when you need per-application wizards for Apache, DNS, or MySQL. Some admins honestly run both.

First-Run Checklist: 10 Steps

1. Install the package with your distro's one-liner (backports on Debian/Ubuntu for the newest release).
2. Enable the socket: sudo systemctl enable --now cockpit.socket.
3. Open the firewall for port 9090 (firewalld service cockpit, or ufw allow 9090/tcp).
4. Visit https://<server-ip>:9090, expect the self-signed certificate warning, and verify the address.
5. Log in with a sudo-enabled system user — root is blocked by default.
6. Click "Limited access" and enter your password to switch to administrative access.
7. Tour the Overview, Logs, Storage, Networking, Accounts, and Services pages.
8. Install the add-ons you need (cockpit-podman, cockpit-files, cockpit-packagekit).
9. Run your first update from the Software Updates page.
10. Lock down access: restrict 9090 to your VPN or put it behind a reverse proxy with authentication.

Sources

• Cockpit project — install, firewall, login and root-default-off instructions (cockpit-project.org/running.html)
• Cockpit project — official applications/add-on packages page (cockpit-project.org/applications)
• Cockpit project — Deployment Guide: port 9090, self-signed certificate generation, multi-host config (cockpit-project.org/guide/latest/guide.html)
• Cockpit project — Cockpit 357 release notes, latest as of late October 2026 (cockpit-project.org/blog/cockpit-357.html)
• Cockpit project — release notes for 322, 326, 327, 329, 332 and 356 (cockpit-project.org/blog/)
• Cockpit project — privileges and the administrative-access toggle (docs.cockpit-project.org/cockpit-guide/latest/guide/privileges.html)
• GitHub — cockpit-project/cockpit: 15,308 stars, LGPL-2.1-or-later (github.com/cockpit-project/cockpit)
• Red Hat — "Getting started with the RHEL web console," RHEL 10 docs (docs.redhat.com)
• ComputingForGeeks — Cockpit walkthrough, tested August 2026 (computingforgeeks.com)
• Reintech — ufw firewall rule for Cockpit (reintech.io)
• Atlantic.net — Cockpit on Debian install guide (atlantic.net/vps-hosting/how-to-install-cockpit-on-debian/)
• SourceForge software comparison — Webmin config-file approach (sourceforge.net/software/compare/)

Frequently Asked Questions

Is Cockpit free?

Yes. Cockpit is free and open source, licensed LGPL-2.1-or-later, and maintained publicly on GitHub with over 15,000 stars. There is no paid tier.

What port does Cockpit use?

Cockpit uses port 9090 over HTTPS. Open it in your firewall — firewall-cmd --add-service=cockpit --permanent on Fedora/RHEL or sudo ufw allow 9090/tcp on Ubuntu/Debian — and browse to https://<server-ip>:9090.

Why does my browser warn about the certificate?

Cockpit generates its own self-signed certificate on first run, so the warning is expected. Verify the address is your server, proceed, and replace it with a real CA-signed certificate for production use.

Can Cockpit manage multiple servers?

The classic in-browser host switcher is being deprecated and is disabled by default on newer distros. Use the Cockpit Client flatpak or the quay.io/cockpit/ws container for multi-server management instead.

Do I need cockpit-pcp for the performance graphs?

No. The cockpit-pcp package is obsolete since Cockpit 326 — the performance graphs on the Overview page are built into the bridge now, so install nothing extra.