Bitbucket Cloud SSL handshake fails without exposing rejected cipher suites

Bitbucket Cloud returns the exact error string “SSL handshake failed” when a TLS connection cannot be established, originating from the Java SSL context during the initial DNS‑resolved host connection.

The error message does not indicate which cipher suites are rejected, leaving operators uncertain whether to upgrade the TLS version or adjust the cipher configuration, and Bitbucket Server’s documentation attributes the same message to certificate chain validation failures.

Which cipher suites are rejected by Bitbucket Cloud’s TLS stack? Can the rejection reason be extracted from the Java SSL debug logs? Is there a way to view the negotiated cipher suite in Bitbucket Cloud’s UI or logs?