[GH-ISSUE #1357] Netbird behind Cloudflare: stream terminated by RST_STREAM #2171

Open
opened 2026-08-05 00:45:42 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @xiaolei0125 on GitHub (Dec 6, 2023).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1357

Describe the problem
I use Cloudflare proxy my netbird management and signal service, But netbird client got disconnect and reconnect every 100 second.

this caused by cloudflare 524 timeoout: https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred.

Error 524 indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 second connection timed out.

Expected behavior
Add grpc keep alive for management and signal service, adapt to a more complex network environment

NetBird status -d output:
Daemon version: 0.24.3
CLI version: 0.24.3
Management: Connected to https://nb.xxx.com:8443/
Signal: Connected to https://nb.xxx.com:8443/
FQDN: m1.nb.iot
NetBird IP: 100.64.0.3/16
Interface type: Kernel
Peers count: 3/4 Connected

Additional context
WARN management/client/grpc.go:158: disconnected from the Management service but will retry silently. Reason: rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: INTERNAL_ERROR
WARN signal/client/grpc.go:151: disconnected from the Signal Exchange due to an error: rpc error: code = Unknown desc = unexpected HTTP status code received from server: 524 (); transport: received unexpected content-type "text/plain; charset=UTF-8"

Related issue
#771
#651

Originally created by @xiaolei0125 on GitHub (Dec 6, 2023). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1357 **Describe the problem** I use Cloudflare proxy my netbird management and signal service, But netbird client got disconnect and reconnect every 100 second. this caused by cloudflare 524 timeoout: https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred. > Error 524 indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 second connection timed out. **Expected behavior** Add grpc keep alive for management and signal service, adapt to a more complex network environment **NetBird status -d output:** Daemon version: 0.24.3 CLI version: 0.24.3 Management: Connected to https://nb.xxx.com:8443/ Signal: Connected to https://nb.xxx.com:8443/ FQDN: m1.nb.iot NetBird IP: 100.64.0.3/16 Interface type: Kernel Peers count: 3/4 Connected **Additional context** ` WARN management/client/grpc.go:158: disconnected from the Management service but will retry silently. Reason: rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: INTERNAL_ERROR` `WARN signal/client/grpc.go:151: disconnected from the Signal Exchange due to an error: rpc error: code = Unknown desc = unexpected HTTP status code received from server: 524 (); transport: received unexpected content-type "text/plain; charset=UTF-8"` **Related issue** #771 #651
saavagebueno added the bug label 2026-08-05 00:45:42 -04:00
Sign in to join this conversation.
No Label bug
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2171