PORT 6379 / TCPDatabase & CacheExposure Risk: Critical

Port 6379: Redis / Valkey — Redis In-Memory Data Store & Cache

Default port for Redis and Valkey. Unauthenticated Redis instances exposed to the internet are immediately compromised.

Default Service

Redis / Valkey

Process: redis-server

Transport Protocol

TCP

IANA Registered Port 6379

Docker Port Flag

-p 6379:6379

Container to Host Mapping

How to Check & Kill Process on Port 6379 (EADDRINUSE Fix)

macOS & Linux (lsof / kill)

# Find process using port 6379
sudo lsof -i :6379

# Instantly kill process on port 6379
lsof -ti:6379 | xargs kill -9

Windows (PowerShell & CMD)

# Find PID listening on port 6379
netstat -ano | findstr :6379

# Force kill by PID
taskkill /PID <PID_NUMBER> /F

Cross-Platform Node.js One-Liner

# Kill port 6379 via npx
npx kill-port 6379

# Or diagnose via Castov CLI
npx castov fix "EADDRINUSE :::6379"

Linux Firewall (UFW) & Connectivity Test

# Test if port 6379 is reachable
nc -zv localhost 6379

# Allow or deny port 6379 in UFW
sudo ufw allow 6379/tcp

Frequently Asked Questions about Port 6379

What is Port 6379 used for?

Port 6379 is the standard network port for Redis / Valkey (Redis In-Memory Data Store & Cache) operating over TCP. The typical system daemon or process is redis-server.

How do I kill a process running on Port 6379 (EADDRINUSE)?

On macOS and Linux, run: lsof -ti:6379 | xargs kill -9 (or npx kill-port 6379). On Windows PowerShell/CMD, run: netstat -ano | findstr :6379 and then taskkill /PID <PID> /F.

Is it safe to expose Port 6379 to the internet?

Port 6379 has a Critical security risk profile. Default port for Redis and Valkey. Unauthenticated Redis instances exposed to the internet are immediately compromised.