A little while ago I shared portop here, my htop-style TUI for figuring out what is actually using your ports. A few people suggested that it would be useful outside the terminal too, especially as a Cockpit page. So I built both. portop v0.1.0 now has a local web dashboard: portop --web It shows sockets, local/remote endpoints, processes, CPU usage, systemd units and Docker containers. You can search and filter the table, inspect a process and see its command line, user, executable, memory, threads and open files. You can also send SIGTERM/SIGKILL after confirmation. I deliberately kept the web server local-only. It binds to loopback, and process details/actions require the token generated when portop starts. And there's now a Cockpit integration too. Install the page and you get: Tools → Ports (portop) directly inside Cockpit, without running another web server. It uses Cockpit's existing bridge and user permissions. So there are now three ways to use portop: portop → terminal UI portop --web → local browser dashboard Cockpit → integrated Ports page The TUI is still the main interface. I just liked the idea of using the same port/process inspection underneath different frontends. Repo: https://github.com/padovanl/portop Thanks to everyone who suggested features after the previous posts. The Cockpit idea in particular came from community feedback.   submitted by   /u/Maleficent_Flight323 [link]   [comments]