Since every Redis URL variation is timing out, I would stop focusing on connection strings and verify the network path itself. Please work through these checks: 1. Verify Redis is healthy * Check Redis logs and confirm it has started successfully and is accepting connections. * If Redis is restarting or crashing, fix that first. 2. Verify internal networking * Open both the Worker and Redis services. * Confirm they are in the same environment and region. * Ensure internal/private networking is enabled. 3. Test DNS resolution from the Worker ```bash nslookup redis ``` or ```bash getent hosts redis ``` If the hostname cannot be resolved, the issue is networking or service discovery. 4. Test raw TCP connectivity ```bash nc -vz redis 6379 ``` If this times out, the Worker cannot reach Redis over the internal network. 5. Verify environment variables ```bash echo $REDIS_HOST echo $REDIS_PORT ``` Make sure the values are resolved correctly and are not still showing template/reference syntax. 6. Test without ioredis Create a minimal TCP connection test using Node's built-in net module. If a plain TCP connection also times out, the problem is below the Redis client layer. Key point: * Authentication issues usually return NOAUTH or WRONGPASS. * DNS issues usually return ENOTFOUND. * ETIMEDOUT generally means the connection never reached Redis at all. If `nc -vz redis 6379` also times out, this strongly points to an internal networking issue rather than a Redis configuration issue.