You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.
Critical error: System.Exception: The request failed because the client was unable to establish connections to 0 endpoints across 1 regions. The client CPU was overloaded during the attempted request.
ActivityId: 8606f3f0-9a24-4c35-9c25-e355b6b6a5d4,
RequestStartTime: 2023-06-13T01:04:48.6225524Z, RequestEndTime: 2023-06-13T01:05:19.0167186Z, Number of regions attempted: 1
According to the Cosmos DB DRI David Noble, it's because we are using SSL 1.0 not SSL 1.2.
I tried to configure the minimum TLS protocol to TLS 1.2, but the issue persists with the same error.
I have the same issue, and using 1.0 is not an option for security reasons.
(And the problem is the client trying to use 1.0, I temproarily downgraded a test-db to 1.1 and then the error complains that the minimum TSL version is 1.1 so the error-message is correct.)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The tool dosen't support data migration to comosdb set with minimum TLS version1.2.
The text was updated successfully, but these errors were encountered: