Stop wondering which process is burning your ports
Networking & Firewall (Ss/Netstat/Iptables/Nftables/Curl)
Stop wondering which process is burning your ports
🧩 The Challenge
You know that feeling when you try to start a service, but it immediately faceplants because the port is already bound to something else? I spent two hours yesterday playing hide-and-seek with a zombie process that kept grabbing port 8080.
💡 The Fix
Instead of guessing which process is hanging onto your socket, use ss to pull the exact process ID straight from the kernel table. It saves you from digging through ps output for ten minutes.
ss -lptn 'sport = :8080'
⚙️ Why It Works
The p flag forces the kernel to reveal the process owner, which is the missing link that standard netstat output often hides. Using the sport filter keeps your terminal clean so you aren’t scrolling through fifty other connections.
🚀 Pro-Tip: Stick a -u on there if you’re chasing down UDP sockets that are acting flaky.
Linux Tips & Tricks | © ngelinux.com | 10/18/2026
