Trading API: TLS handshake reset (ECONNRESET) for local clients; browsers work

[joseluisacosta93]

Summary

Local non-browser clients cannot complete a TLS handshake with https://sports-api.cloudbet.com. The connection is reset before any HTTP response.

Reproduction

• curl: (35) Recv failure: Connection was reset; HTTP status 000
• Node.js and Postman Desktop: ECONNRESET
• OpenSSL and .NET: reset after ClientHello, before ServerHello
• Browsers on the same PC and a phone reach the root URL and receive the expected 404 backend NotFound
• Postman Cloud Agent also receives that 404
• Reproduces over both home internet and a mobile hotspot
• TLS 1.2, HTTP/1.1, and HTTP/2 were tested
• No API key or authenticated endpoint was used in these probes

A same-edge-IP OpenSSL differential returns a TLS alert without SNI, but resets after ClientHello when SNI is sports-api.cloudbet.com.

Questions

1. Is a source IP/ASN, region, or TLS-client policy terminating non-browser TLS connections before HTTP?
2. What client/network configuration is officially supported for the Trading API?
3. Is there any additional diagnostic (for example, a packet-capture timestamp) your network team needs?

I do not want to bypass geographic or security controls. I will not post my API key publicly.