Troubleshoot Redis
Diagnose connectivity, authentication, and import problems.
The client cannot reach the instance
Check runtime status and confirm the chosen endpoint matches the client's location. Private hostnames require project-network connectivity. External clients need an enabled TLS endpoint, correct SNI hostname, and the displayed port.
Review Firewall Policy against the client's public outbound address. A blocked TCP connection may close without a descriptive error page.
Authentication fails
Use both the managed customer username and password from Connection. After rotation, reload the details and update all application secrets. Do not assume that the username remains unchanged.
TLS verification fails
Check the hostname, SNI, system time, and trusted CA configuration. Use a TLS-capable Redis client and preserve the external hostname. Correct certificate trust instead of disabling verification.
Import fails
Confirm that the source is standalone Redis, reachable by the import service, and permits the required commands. Check source database selection, destination emptiness, key count, transfer size, and execution time. Inspect for partial destination data before retrying.
Credentials or operations remain unavailable
Wait for provisioning or the active operation to finish, then refresh. If the state persists, contact support with the resource ID, operation, and error text, without passwords or credential-bearing URIs.