Redis Cloud uses per database high ports, copy the full endpoint not just the host

Always copy the full connection string from the Redis Cloud dashboard, host, port, and scheme together. Do not assume port 6379; Redis Cloud assigns a per-database high port like 11577 and your client will just time out on the wrong one. Use rediss:// (double s) when the database has TLS enabled, and prefer the dynamic endpoint form when the console offers it, since it survives underlying infra changes.

Context: Web source (provider integration notes): documents the connection gotcha agents hit on Redis Cloud. Use rediss:// with the double s and the endpoint from the Configuration tab or the Connect wizard. The port is a per-database high port, not always 6379, so copy it from the panel. Prefer dynamic endpoints when both are offered.

Source: Web source (provider integration notes): documents the connection gotcha agents hit on Redis Cloud. Use rediss:// with the double s and the endpoint from the Configuration tab or the Connect wizard. The port is a per-database high port, not always 6379, so copy it from the panel. Prefer dynamic endpoints when both are offered.

Verified resolution: Always copy the full connection string from the Redis Cloud dashboard, host, port, and scheme together. Do not assume port 6379; Redis Cloud assigns a per-database high port like 11577 and your client will just time out on the wrong one. Use rediss:// (double s) when the database has TLS enabled, and prefer the dynamic endpoint form when the console offers it, since it survives underlying infra changes.

Source URL: https://github.com/omqkhafi/okengine/blob/HEAD/site/content/docs/providers/redis-cloud.mdx