Port 6379 REDIS
Port 6379 is the IANA-assigned redis port for An advanced key-value cache and store (TCP).
What is port 6379 used for?
Port 6379 is assigned to redis and uses TCP. The IANA registry describes the service as “An advanced key-value cache and store”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.
Ports are the transport-layer address a service listens on. A client that wants to reach redis connects to port 6379. If nothing is listening, the connection is refused. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 6379 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Browse all Caching and in-memory stores ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Salvatore_Sanfilippo].
Check and block port 6379
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :6379'Check on Windows
Get-NetTCPConnection -LocalPort 6379 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 6379/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 6379 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 6379 safe to expose?
Redis has no authentication by default and is a top target for crypto-mining and data-theft campaigns. Bind it to localhost and require a password. Treat this port as sensitive. Restrict it to trusted networks or a VPN, require authentication and logging, and never expose it directly to the public internet without a hardened gateway in front.
Where port 6379 is usually used
Most traffic on port 6379 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Session storage, rate limiting and hot-key caching in front of a slower database.
- Several application instances sharing counters or job state on port 6379.
- Local development stacks that run the cache in a container.
Ping Redis
A successful PONG means the cache is reachable and responding to commands.
redis-cli -h 127.0.0.1 -p 6379 ping
Common problems with port 6379
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 6379. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :6379' or sudo lsof -i :6379. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 6379 at a glance
| Port number | 6379 |
|---|---|
| Service name | redis |
| Transport protocol | TCP |
| Category | Caching and in-memory stores |
| Range | Registered port (1024–10000) |
| Risk level | High |
| Registered assignee | [Salvatore_Sanfilippo] |
| Registry description | An advanced key-value cache and store |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 6379 used for?
Port 6379 (REDIS) uses TCP. An advanced key-value cache and store.
How do I check if port 6379 is open?
On Linux run `sudo ss -tlpn 'sport = :6379'`. On Windows run `Get-NetTCPConnection -LocalPort 6379 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 6379; empty output usually means nothing is bound to it.
How do I block port 6379?
With UFW run `sudo ufw deny 6379/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 6379 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 6379 safe to expose?
Redis has no authentication by default and is a top target for crypto-mining and data-theft campaigns. Bind it to localhost and require a password. Nevertheless, treat this port as sensitive. Restrict it to trusted networks or a VPN, require authentication and logging, and never expose it directly to the public internet without a hardened gateway in front.
Related ports
- Port 6370 · metaedit-seMetaEdit+ Server Administration
- Port 6400 · boe-cmsBusiness Objects CMS contact port
- Port 1388 · objective-dbcObjective Solutions DataBase Cache
- Port 7001 · afs3-callbackcallbacks to cache managers
- Port 7009 · afs3-rmtsysremote cache manager service
- Port 8276 · ms-mccMicrosoft Connected Cache
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy