Port 6379 — Redis

TCPDatabase

Redis commonly uses TCP 6379. Restrict access to trusted clients; a cache can still contain sensitive data and powerful management commands.

Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.

Configuration and troubleshooting

Review bind, port, protected-mode, ACLs and TLS. With Docker publishing, inspect host mappings and bind addresses as well as the container listener.

Important limitations

Do not disable protected-mode as a default connectivity fix or place credentials in commands that may be logged or shared.

Read-only checks: run on the server host

Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.

Linux

sudo ss -ltnp 'sport = :6379'

macOS

sudo lsof -nP -iTCP:6379 -sTCP:LISTEN

Windows PowerShell

Get-NetTCPConnection -LocalPort 6379 -State Listen

Sources and review

Sources checked on:

This review covers the explanations and sources on this page, not your device or every community software entry below.

Software Using This Port (2 software)

Community software entries: links are references, not individual verification.

Redis

Default port for Redis in-memory database

Reference link ↗

Feast Redis

FeastStorageRedisPort

Reference link ↗

Usage Suggestions

  • Before using port 6379, please confirm it is not occupied by other services
  • If you encounter port conflicts, consider using other ports or stopping the occupying service

Quick Info

Port
6379
Protocol
TCP
Categories
Database
Usage Status
2 software in use

Related Ports

Port 5432TCP
→
Port 27017TCP
→

Need Help?

If you find incorrect information or need to add more, please submit correction information.

Submit Correction