PORT 5173 / TCPDev & LocalhostExposure Risk: Low
Port 5173: Vite Dev Server — Vite Frontend Build Tool (React, Vue, Svelte)
Default hot-module-replacement (HMR) development server port for Vite.
Default Service
Vite Dev Server
Process: node
Transport Protocol
TCP
IANA Registered Port 5173
Docker Port Flag
-p 5173:5173
Container to Host Mapping
How to Check & Kill Process on Port 5173 (EADDRINUSE Fix)
macOS & Linux (lsof / kill)
# Find process using port 5173 sudo lsof -i :5173 # Instantly kill process on port 5173 lsof -ti:5173 | xargs kill -9
Windows (PowerShell & CMD)
# Find PID listening on port 5173 netstat -ano | findstr :5173 # Force kill by PID taskkill /PID <PID_NUMBER> /F
Cross-Platform Node.js One-Liner
# Kill port 5173 via npx npx kill-port 5173 # Or diagnose via Castov CLI npx castov fix "EADDRINUSE :::5173"
Linux Firewall (UFW) & Connectivity Test
# Test if port 5173 is reachable nc -zv localhost 5173 # Allow or deny port 5173 in UFW sudo ufw allow 5173/tcp
Frequently Asked Questions about Port 5173
What is Port 5173 used for?
Port 5173 is the standard network port for Vite Dev Server (Vite Frontend Build Tool (React, Vue, Svelte)) operating over TCP. The typical system daemon or process is node.
How do I kill a process running on Port 5173 (EADDRINUSE)?
On macOS and Linux, run: lsof -ti:5173 | xargs kill -9 (or npx kill-port 5173). On Windows PowerShell/CMD, run: netstat -ano | findstr :5173 and then taskkill /PID <PID> /F.
Is it safe to expose Port 5173 to the internet?
Port 5173 has a Low security risk profile. Default hot-module-replacement (HMR) development server port for Vite.