Skip to main content
Solved

Problem connecting Worker node to the leader node

  • November 11, 2025
  • 1 reply
  • 94 views

Dinesh Kumar

I'm seeking assistance with connecting a Cribl Stream worker (running on a GCP VM) to our Cribl Cloud Leader. We are encountering a persistent connection handshake timeout error, despite extensive troubleshooting that indicates the network path through our corporate proxy is otherwise functional.

Environment Details:

  • Cribl Version: Latest (installed via install-worker.sh script)
  • Worker OS: Ubuntu (GCP VM)

{"time":"2025-11-11T17:11:14.026Z","cid":"api","channel":"ProcessMetrics","level":"info","message":"stats","cpuPerc":0.69,"eluPerc":0.41,"mem":{"heap":108,"heapTotal":117,"ext":3,"rss":201,"buffers":0}}

{"time":"2025-11-11T17:11:16.589Z","cid":"api","channel":"MetricsStore","level":"info","message":"active metrics","numMetrics":29}

{"time":"2025-11-11T17:11:23.433Z","cid":"api","channel":"output:DistWorker","level":"warn","message":"sending is blocked","since":1762880150,"elapsed":932,"endpoint":{"host":"main-lucid-turcic-cir6n25.cribl.cloud","port":4200,"tls":true,"rejectUnauthorized":false}}

^[{"time":"2025-11-11T17:11:43.549Z","cid":"api","channel":"output:DistWorker","level":"info","message":"attempting to connect","host":"main-lucid-turcic-cir6n25.cribl.cloud","port":4200,"tls":true,"rejectUnauthorized":false}

{"time":"2025-11-11T17:11:43.549Z","cid":"api","channel":"output:DistWorker","level":"debug","message":"connecting","host":"main-lucid-turcic-cir6n25.cribl.cloud","port":4200,"tls":true,"rejectUnauthorized":false}

{"time":"2025-11-11T17:11:43.644Z","cid":"api","channel":"HBChannelClient","level":"info","message":"Resolved dns address","hostname":"main-lucid-turcic-cir6n25.cribl.cloud","family":4,"address":"3.22.195.63"}

{"time":"2025-11-11T17:11:50.743Z","cid":"api","channel":"HBChannelClient","level":"info","message":"metric sender","total":15,"failed":0,"dropped":0}

{"time":"2025-11-11T17:11:53.438Z","cid":"api","channel":"output:DistWorker","level":"warn","message":"sending is blocked","since":1762880150,"elapsed":962,"endpoint":{"host":"main-lucid-turcic-cir6n25.cribl.cloud","port":4200,"tls":true,"rejectUnauthorized":false}}

{"time":"2025-11-11T17:11:53.644Z","cid":"api","channel":"output:DistWorker","level":"debug","message":"will retry to connect","nextConnectTime":1762881173644}

{"time":"2025-11-11T17:11:53.654Z","cid":"api","channel":"output:DistWorker","level":"error","message":"connection error","error":"connection handshake timeout, dst=main-lucid-turcic-cir6n25.cribl.cloud:4200","endpoint":{"host":"main-lucid-turcic-cir6n25.cribl.cloud","port":4200,"tls":true,"rejectUnauthorized":false}}

  • Connectivity Requirement: All outbound internet traffic from the VM must pass through a corporate HTTP/HTTPS proxy

Are there any known issues or specific configurations required for Cribl workers connecting via corporate HTTP/HTTPS proxies,

Best answer by kprior

Hey Dinesh! I believe this is likely related to those questions around the SOCKS proxy we discussed previously. For other people’s awareness: the management plane of worker→ leader connectivity requires TCP rather than HTTP. Therefore, if a proxy is required, it must be a SOCKS proxy. Here is some more information on that: https://docs.cribl.io/stream/proxy-socks-config/ . If this is NOT related to this problem, please let me know, though. 

 

 

1 reply

kprior
  • Employee
  • Answer
  • November 18, 2025

Hey Dinesh! I believe this is likely related to those questions around the SOCKS proxy we discussed previously. For other people’s awareness: the management plane of worker→ leader connectivity requires TCP rather than HTTP. Therefore, if a proxy is required, it must be a SOCKS proxy. Here is some more information on that: https://docs.cribl.io/stream/proxy-socks-config/ . If this is NOT related to this problem, please let me know, though.