a day ago
Outbound HTTPS connections from my service to Cloudflare R2 (*.r2.cloudflarestorage.com) consistently fail with SSLV3_ALERT_HANDSHAKE_FAILURE at the TLS handshake stage — confirmed across 4 independent Python SSL/HTTP libraries (raw ssl module, requests, httpx, boto3), so it's not a code-level issue. OpenSSL 3.5.6, Python 3.13.13. Other outbound connections (MongoDB Atlas) work fine. This suggests a network-level block or proxy interference specific to R2's endpoint.
1 Replies
a day ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 1 day ago
an hour ago
Your code is fine. Cloudflare R2 is intentionally hanging up the connection during the security handshake, likely for two reasons: IP Blocking: Railway uses shared outgoing IP addresses. If another app abused Cloudflare from that same IP, Cloudflare blacklisted it. Your app is caught in the crossfire. Security Code Mismatch: Your cutting-edge software (OpenSSL 3.5.6) and Cloudflare cannot agree on a matching security "cipher. "How to fix it: Redeploy on Railway: This assigns a fresh IP address, instantly bypassing the block. Force standard ciphers: Restrict Python's SSL context strictly to TLS_AES_256_GCM_SHA384 in your connection script.