Skip to content

Connection reset when sending events from Huawei Cloud to ingest.us.sentry.io #108310

@sulhadin

Description

@sulhadin

Environment

SaaS (https://sentry.io/)

What are you trying to accomplish?

We're trying to send error events from our Node.js application running on Huawei Cloud (Kubernetes/CCE) to Sentry. Our DSN uses the ingest.us.sentry.io endpoint (org: o308413).

How are you getting stuck?

We're trying to send error events from our Node.js application running on Huawei Cloud (Kubernetes/CCE) to Sentry. Our DSN uses the ingest.us.sentry.io endpoint (org: o308413).


How are you getting stuck?

We're getting ECONNRESET errors when the Sentry SDK tries to send events:

Sentry Logger [error]: Error while sending envelope: Error: read ECONNRESET
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}

Test results from inside the pod:

Endpoint | IP | Result -- | -- | -- sentry.io | 35.186.247.156 | ✅ Success o308413.ingest.us.sentry.io | 34.160.81.0 | ❌ Connection reset by peer
bash
$ curl -v --ipv4 --connect-timeout 10 https://o308413.ingest.us.sentry.io/
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* Recv failure: Connection reset by peer
curl: (35) Recv failure: Connection reset by peer

Key observations:

  • The same application works perfectly from AWS — events are delivered successfully
  • Only Huawei Cloud environment fails
  • Connection is reset during TLS handshake, before any HTTP request is made
  • DNS resolves correctly, the issue is at the TCP/TLS level

Question:
Is there any geo-blocking, IP filtering, or rate-limiting on Sentry's ingest infrastructure that might affect requests from Huawei Cloud? We suspect our egress IPs may be blocked — if needed, we can share them privately with the Sentry team.
Environment:

Sentry SDK: @sentry/node
Platform: Huawei Cloud CCE (Kubernetes)
Ingest endpoint: ingest.us.sentry.io

Where in the product are you?

Help

Link

No response

DSN

No response

Version

No response

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Waiting for: Support

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions