PORT 5672 / TCPInfrastructure & CloudExposure Risk: High
Port 5672: RabbitMQ (AMQP) — Advanced Message Queuing Protocol
Default port for RabbitMQ message broker connections.
Default Service
RabbitMQ (AMQP)
Process: beam.smp
Transport Protocol
TCP
IANA Registered Port 5672
Docker Port Flag
-p 5672:5672
Container to Host Mapping
How to Check & Kill Process on Port 5672 (EADDRINUSE Fix)
macOS & Linux (lsof / kill)
# Find process using port 5672 sudo lsof -i :5672 # Instantly kill process on port 5672 lsof -ti:5672 | xargs kill -9
Windows (PowerShell & CMD)
# Find PID listening on port 5672 netstat -ano | findstr :5672 # Force kill by PID taskkill /PID <PID_NUMBER> /F
Cross-Platform Node.js One-Liner
# Kill port 5672 via npx npx kill-port 5672 # Or diagnose via Castov CLI npx castov fix "EADDRINUSE :::5672"
Linux Firewall (UFW) & Connectivity Test
# Test if port 5672 is reachable nc -zv localhost 5672 # Allow or deny port 5672 in UFW sudo ufw allow 5672/tcp
Frequently Asked Questions about Port 5672
What is Port 5672 used for?
Port 5672 is the standard network port for RabbitMQ (AMQP) (Advanced Message Queuing Protocol) operating over TCP. The typical system daemon or process is beam.smp.
How do I kill a process running on Port 5672 (EADDRINUSE)?
On macOS and Linux, run: lsof -ti:5672 | xargs kill -9 (or npx kill-port 5672). On Windows PowerShell/CMD, run: netstat -ano | findstr :5672 and then taskkill /PID <PID> /F.
Is it safe to expose Port 5672 to the internet?
Port 5672 has a High security risk profile. Default port for RabbitMQ message broker connections.