Networking & Firewall (Ss/Netstat/Iptables/Nftables/Curl)

Catch the exact PID blocking your firewall ports

🧩 The Challenge

You’ve definitely spent way too long staring at a port that refuses to bind, only to realize some zombie process from an old deployment is still hogging it. It’s annoying as hell when you can’t tell which service is actually holding the file descriptor.

💡 The Fix

Stop guessing which process is causing the conflict by using the right flag in your socket statistics tool. You’ll see the process ID and name mapped directly to the active ports in one view.

sudo ss -tulpn

⚙️ Why It Works

Adding the -p flag forces the kernel to reveal the process context for every open socket, which saves you from grepping through ps outputs for ten minutes. It’s the fastest way to verify who is actually listening on your interface.

🚀 Pro-Tip: Pipe that into grep if you are hunting for a specific port number so you don’t have to scroll through the whole list.

Linux Tips & Tricks | © ngelinux.com | 8/15/2026