Saltar al contenido

Puerto6379— Redis

Redis suele usar TCP 6379. Restrinja el acceso a clientes de confianza; una caché también puede contener datos sensibles y comandos administrativos potentes.

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

Configuration and troubleshooting

Revise bind, port, protected-mode, las ACL y TLS. Al publicar puertos con Docker, compruebe las asignaciones del host y las direcciones de enlace además del socket de escucha del contenedor.

Important limitations

No desactive protected-mode como solución habitual a problemas de conexión ni incluya credenciales en comandos que puedan registrarse o compartirse.

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 que utiliza este puerto (2 programas)

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

Redis

Default port for Redis in-memory database

Feast Redis

FeastStorageRedisPort

Recomendaciones de uso

  • Antes de utilizar el puerto 6379, comprueba que no esté ocupado por otros servicios
  • Si encuentras conflictos de puertos, considera utilizar otros puertos o detener el servicio que lo ocupa

Preguntas frecuentes

What is port 6379 used for?

Port 6379 sits in the Database category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.

Is port 6379 TCP or UDP?

The registered protocol on this page is TCP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.

How do I check if port 6379 is in use?

On Linux: sudo ss -tlnp 'sport = :6379' for an exact port match. On macOS: sudo lsof -nP -iTCP:6379 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 6379 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.

Is port 6379 secure? Should I open it in my firewall?

A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication. The caution section on this page lists port-specific risks.

Información rápida

Puerto
6379
Protocolo
TCP
Categorías
Bases de datos
Estado de uso
2 programas que lo utilizan

¿Necesitas ayuda?

Si encuentras información incorrecta o necesitas añadir más, envíanos una corrección.

Enviar una corrección