How do I kill the process using port 2379?

On macOS & Linux, run: "sudo systemctl stop etcd || kill -9 $(lsof -t -i:2379)". On Windows PowerShell (as Admin), run: "Stop-Process -Id (Get-NetTCPConnection -LocalPort 2379).OwningProcess -Force".

Why am I getting "port 2379 already in use" (EADDRINUSE)?

This occurs when another background instance of etcd or a zombie process is already bound to port 2379. Use the kill commands above to free the port immediately.

DevOps & Cloud

Risk: Critical

Port 2379 — etcd Client API (Kubernetes Datastore)

Q: Is Port 2379 safe to expose to the public internet?

Risk level is Critical. Direct unauthenticated access to etcd port 2379 grants full administrative control over the Kubernetes cluster, including access to all cluster secrets and certificates. Always enforce mTLS.

Port 2379 is the primary gRPC client communication port for etcd, the distributed key-value store that houses the entire state and secret configuration of Kubernetes clusters.

PORT NUMBER

2379

PROTOCOL

TCP

DEFAULT PROCESS

etcd

FIREWALL TARGET

2379/tcp

Instant Terminal Fixes for Port 2379

macOS & Linux Terminal

1. Check who is listening on port 2379:

etcdctl endpoint health || sudo lsof -i :2379

2. Kill process occupying port 2379 (EADDRINUSE fix):

sudo systemctl stop etcd || kill -9 $(lsof -t -i:2379)

3. UFW Firewall Allow rule:

sudo ufw deny 2379/tcp

Windows PowerShell (Admin)

1. Check listening port:

Get-NetTCPConnection -LocalPort 2379

2. Force kill process on port 2379:

Stop-Process -Id (Get-NetTCPConnection -LocalPort 2379).OwningProcess -Force

3. Docker Port Forwarding Mapping:

docker run -d -p 2379:2379 quay.io/coreos/etcd:latest

Common Error Encountered

rpc error: code = Unavailable desc = connection refused to etcd cluster on port 2379.

Security Advisory & Hardening

Direct unauthenticated access to etcd port 2379 grants full administrative control over the Kubernetes cluster, including access to all cluster secrets and certificates. Always enforce mTLS.

Frequently Asked Questions

Port 2379 Questions & Answers

Common questions regarding default services, kill commands, and firewall configurations.

Port 2379 is commonly used for etcd Client API (Kubernetes Datastore). Port 2379 is the primary gRPC client communication port for etcd, the distributed key-value store that houses the entire state and secret configuration of Kubernetes clusters.

Explore Other Developer Ports

View All Ports Directory

Port 3000React Port 8080HTTP Alternate Port 5173Vite Dev Server (Vue, Svelte, React)Port 80HTTP (Hypertext Transfer Protocol)Port 443HTTPS (HTTP over TLS Port 5000Flask