Isolated Handshake Failure (SSL) with Endpoints - Reason: Write EPROTO - SSL Alert Number 40

Last Updated: Jul 31, 2024

Overview

This article addresses the situation in which there is an SSL alert about handshake failures. Those failures are isolated in time (1 per month or so) and appear when calling Management APIv2 or Authentication API.

The following error is seen:

FetchError: request to https://TENANT/api/v2/users failed, reason: write EPROTO 139886319032192:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:…/deps/openssl/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 40

Applies To

  • Handshake failure
  • SSL alert

Solution

Due to the internet’s adaptive nature, the levels of latency or error rates of some endpoints can fluctuate to accommodate anomalies that occur due to increased traffic or operational maintenance. In most cases, the Auth0 system detects and automatically adjusts to these hiccups in a very short time. However, it is not instantaneous; therefore, customers may periodically experience short degrades or increases in errors on one or more endpoints during these adjustments.

As these are normal, expected occurrences, Auth0 does not investigate these unless they either violate the SLA for a particular endpoint or are ongoing, prolonged, or reoccurring issues that are causing long-term challenges for a customer.