Temporal

Failed reaching server error during TLS certificate expiration or startup

critical
Connection ManagementUpdated Mar 3, 2026

The 'Failed reaching server: last connection error' message indicates connectivity failures that commonly occur due to expired TLS certificates or during Server startup when roles are not fully initialized. This prevents Clients and Workers from establishing connections.

Technologies:
How to detect:

Connection attempts from Clients or Workers fail with 'Failed reaching server: last connection error'. This typically occurs when TLS certificates have expired or during Server startup phase before roles are fully initialized.

Recommended action:

1. Check TLS certificate expiration dates immediately using certificate inspection tools. 2. If certificates are expired, renew and deploy new certificates following your certificate management procedures. 3. If error occurs during startup, verify this is transient by waiting for Server initialization to complete (typically a few seconds to minutes). 4. Monitor certificate expiration proactively using the temporal_server_certificates_expiring metric to renew before expiration. 5. Implement automated certificate renewal processes to prevent future expirations. 6. If startup-related, consider implementing retry logic in Clients/Workers to handle temporary unavailability during deployments.