Networking & Firewall (Ss/Netstat/Iptables/Nftables/Curl)
Stop ss from hiding the process that is actually killing your ports
🧩 The Challenge
You are staring at a port that refuses to bind because something is already listening, but netstat just shows a PID of – or hides the owner entirely. It drives me up the wall when I know a service is running but the tools act like it’s a ghost in the machine.
đź’ˇ The Fix
Use the internal process flag with ss so it actually requests the UID and PID info from the kernel. It’s the difference between guessing which binary is hogging the port and knowing exactly which one to kill.
sudo ss -lptn⚙️ Why It Works
Adding the -p flag forces the socket statistics tool to look up the process associated with each connection. Since you’re usually checking these as a normal user, that sudo prefix is the only way you’ll see the full truth instead of empty brackets.
🚀 Pro-Tip: Pipe it into grep if you are hunting a specific port range to avoid drowning in noise.
Linux Tips & Tricks | © ngelinux.com | 8/7/2026