Guides
Practical port problems, answered honestly.
Short, accurate write-ups for Windows and Linux. Each one maps to something PortPilot actually does.
- How to find what is using a port on WindowsSee which process is listening on a TCP port on Windows using PortPilot, plus netstat as a fallback.
- How to find what is using a port on LinuxIdentify the process listening on a port on Linux with PortPilot, ss, or lsof.
- How to kill a process using a portStop the process holding a port with PortPilot ProcessGuard, or fall back to OS tools.
- How to check open ports on WindowsList listening ports on Windows with PortPilot or netstat.
- How to check open ports on LinuxList listening ports on Linux with PortPilot or ss.
- How to troubleshoot port conflictsResolve EADDRINUSE and port-already-allocated errors with PortPilot health and process identity.
- How to expose a local development serverShare a local port through PortPilot’s ngrok integration (Pro).
- How to manage Docker portsSee which host ports Docker published — PortPilot is read-only awareness, not Compose control.
- How to manage development portsKeep local dev servers, databases, and front-end tooling visible in one PortPilot view.
- How to troubleshoot localhost portsDebug 127.0.0.1 vs 0.0.0.0 binds, failed loopback HTTP, and stale processes.