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

Find which process is binding to that phantom port

🧩 The Challenge

You are trying to spin up a service and it keeps screaming that the port is already in use, but a quick grep through your config files shows nothing listening on that socket. I have spent way too many nights rebooting servers just to clear up a port conflict that wasn’t actually there.

💡 The Fix

Use the socket statistics tool with the right flags to force it to show you the process ID attached to those specific ports. It cuts through the noise and stops you from guessing which daemon is holding onto your resources.

sudo ss -tulpn | grep :8080

⚙️ Why It Works

Adding the -p flag to your ss command forces the kernel to report the process name and PID associated with every open socket. Seeing exactly which binary is hogging the port saves you from having to kill random services just to find the culprit.

🚀 Pro-Tip: Use the -n flag if you don’t want to wait for ss to try and resolve DNS names for every single connection.

Linux Tips & Tricks | © ngelinux.com | 11/5/2026