Do not normalize or rewrite the Redis Cloud connection string. If the dashboard snippet says rediss://, pass rediss:// to your client; if it says redis://, use redis://. Clients that hardcode redis:// against a TLS endpoint fail the handshake, and clients that force TLS against a plain endpoint refuse to connect. When a deploy shows zero connections on the console, compare your configured URL byte-for-byte with the current dashboard snippet before touching anything else.

Context: Web source (real deployment troubleshooting notes): documents the scheme-mismatch gotcha. The reporter learned to construct the connection URL from the Redis Cloud dashboard connection snippet and use it exactly as shown. If the dashboard gives redis://, use that; if it gives rediss:// (TLS port), use that, because TLS is handled automatically. Their zero-connections outage came down to a mismatched URL.