Toolman 100% local

Port 6379 — Redis

TCP registered

What runs on port 6379

The default Redis port.

Redis. Until version 6 there was no user model at all and, in default configurations, no password either — anyone who could reach the port had complete control. Redis can write files to arbitrary paths, so that control has repeatedly been turned into remote code execution by writing an SSH key or a cron entry. Modern versions bind to localhost and enable protected mode by default; the danger is old configurations and containers that override it.

Security considerations

Redis historically had no authentication and binds to all interfaces if misconfigured. Exposed instances are routinely used to plant SSH keys and cryptominers. Bind to localhost and set a password.

Checking whether something is listening

# Linux / macOS — what is bound to the port
sudo lsof -i :6379
sudo ss -lntp | grep :6379

# Windows
netstat -ano | findstr :6379
Get-NetTCPConnection -LocalPort 6379

# is it reachable from outside?
nc -zv example.com 6379
curl -v telnet://example.com:6379

Freeing the port

# find the process, then stop it
sudo lsof -ti :6379 | xargs kill        # Linux / macOS
netstat -ano | findstr :6379            # note the PID, then:
taskkill /PID <pid> /F                    # Windows

Should this port be open to the internet?

No. Port 6379 should never be reachable from a public address. Bind it to localhost or a private network, and reach it through a VPN or bastion host if remote access is genuinely needed. Internet-wide scanners find newly exposed instances of this service within minutes.

Opening or blocking port 6379

There is no blanket-allow rule on this page, because there is no case for one. Redis on port 6379 should be reachable from named addresses or not at all, so what follows restricts rather than opens:

# ufw — Debian, Ubuntu
sudo ufw allow from 10.0.0.0/8 to any port 6379 proto tcp
sudo ufw deny 6379/tcp                    # everything else

# firewalld — RHEL, Fedora, CentOS
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=6379 protocol=tcp accept'
sudo firewall-cmd --reload

# iptables, if you are still there
sudo iptables -A INPUT -p tcp --dport 6379 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 6379 -j DROP

# Windows
New-NetFirewallRule -DisplayName "Redis 6379" -Direction Inbound -Protocol TCP -LocalPort 6379 -RemoteAddress 10.0.0.0/8 -Action Allow

Change 10.0.0.0/8 to whatever your private range actually is. A firewall rule is the second line: the first is binding the service to a private interface, because a service that only listens on 127.0.0.1 cannot be reached however the firewall is configured.

Quick reference

Port6379
ProtocolTCP
ServiceRedis
RangeRegistered (1024–49151) — any user process may bind

Frequently asked questions

What is port 6379 used for?

The default Redis port.

Is it safe to open port 6379?

Redis historically had no authentication and binds to all interfaces if misconfigured. Exposed instances are routinely used to plant SSH keys and cryptominers. Bind to localhost and set a password.

How do I check if port 6379 is open?

Locally, sudo lsof -i :6379 on macOS or Linux, or netstat -ano | findstr :6379 on Windows. From outside, nc -zv host 6379 tells you whether anything answers.

Why do I get "address already in use" on port 6379?

Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :6379 and stop it, or configure your application to use a different port.

Can I change the port this service uses?

Almost always yes, in the service's configuration. Moving off a default port reduces automated scan noise, but it is obfuscation rather than security — a real attacker scans all 65,535.

Other common ports

All port numbers