Summary
Our deployment uses a TLS-only Redis (managed cloud instance). The open-source livekit/sip binary (image/binary below) consistently initiates a plaintext connection to Redis. There is no knob to make it use TLS via config.yaml. The Redis endpoint immediately resets the connection (read: connection reset by peer), which is expected if the client isn’t speaking TLS. I can establish a TLS handshake to the same host/port with openssl s_client, so reachability and certificates look fine.
Request
Confirm whether the open-source SIP server currently supports TLS to Redis.
If it should: guidance on the exact config keys the SIP binary expects (YAML and env names).
If it does not yet support Redis TLS in open source: could you mark this as a feature request and (ideally) document the current limitation in the README/self-hosting docs? A minimal fix would be wiring the tls.enabled, tls.server_name, and tls.insecure options (or honoring rediss://) through to the Redis client used by SIP.
Extra notes
From the README / self-hosting docs, the SIP config examples only show redis.address/username/password/db and don’t mention TLS options, which may be part of the confusion. (If TLS is supported, adding a snippet would help discoverability.)
My Logs
SIP version 0.0.1
2025-10-02T14:18:59Z INFO sip redis/redis.go:142 connecting to redis {"nodeID":"NE_...", "simple": true, "addr":":6379"}
unable to connect to redis: read: connection reset by peer
Summary
Our deployment uses a TLS-only Redis (managed cloud instance). The open-source livekit/sip binary (image/binary below) consistently initiates a plaintext connection to Redis. There is no knob to make it use TLS via config.yaml. The Redis endpoint immediately resets the connection (read: connection reset by peer), which is expected if the client isn’t speaking TLS. I can establish a TLS handshake to the same host/port with openssl s_client, so reachability and certificates look fine.
Request
Confirm whether the open-source SIP server currently supports TLS to Redis.
If it should: guidance on the exact config keys the SIP binary expects (YAML and env names).
If it does not yet support Redis TLS in open source: could you mark this as a feature request and (ideally) document the current limitation in the README/self-hosting docs? A minimal fix would be wiring the tls.enabled, tls.server_name, and tls.insecure options (or honoring rediss://) through to the Redis client used by SIP.
Extra notes
From the README / self-hosting docs, the SIP config examples only show redis.address/username/password/db and don’t mention TLS options, which may be part of the confusion. (If TLS is supported, adding a snippet would help discoverability.)
My Logs
SIP version 0.0.1
2025-10-02T14:18:59Z INFO sip redis/redis.go:142 connecting to redis {"nodeID":"NE_...", "simple": true, "addr":":6379"}
unable to connect to redis: read: connection reset by peer