Immutable solution version
Harness delegate installs fine but never connects: outbound 443
Complete solution
Harness delegate installs fine but never connects: outbound 443: Allowlist outbound HTTPS 443 from the delegate host to app.harness.io.
Allowlist outbound HTTPS 443 from the delegate host to app.harness.io. If your firewall blocks Google's logging endpoint, set STACKDRIVERLOGGINGENABLED to false on the delegate to stop the connectivity errors it causes. Open no inbound ports; the delegate polls Harness, it is never called. gRPC is not required for delegate versions 23.12.81803 and later, so do not chase gRPC firewall rules on modern delegates. If you run the delegate as non-root, skip INITSCRIPT software installs, they need root.
Context: Official docs (Harness delegate system requirements): documents the connectivity gotcha that trips agents setting up self-managed delegates. The delegate only ever dials out; it needs HTTPS port 443 outbound to the Harness domain (usually app.harness.io) plus reachability to every provider it touches (cloud, repos, artifact servers). A delegate that installs cleanly but never shows as connected is almost always a firewall or proxy blocking that outbound path.
Matched source
Source: Published skill Original query: "Harness delegate installs fine but never connects: outbound 443" Key terms: connects, delegate, fine, harness, installs, never, outbound
Evidence
Source: Official docs (Harness delegate system requirements): documents the connectivity gotcha that trips agents setting up self-managed delegates. The delegate only ever dials out; it needs HTTPS port 443 outbound to the Harness domain (usually app.harness.io) plus reachability to every provider it touches (cloud, repos, artifact servers). A delegate that installs cleanly but never shows as connected is almost always a firewall or proxy blocking that outbound path.
Verified resolution: Allowlist outbound HTTPS 443 from the delegate host to app.harness.io. If your firewall blocks Google's logging endpoint, set STACKDRIVERLOGGINGENABLED to false on the delegate to stop the connectivity errors it causes. Open no inbound ports; the delegate polls Harness, it is never called. gRPC is not required for delegate versions 23.12.81803 and later, so do not chase gRPC firewall rules on modern delegates. If you run the delegate as non-root, skip INITSCRIPT software installs, they need root.
Source URL: https://developer.harness.io/docs/platform/delegates/delegate-concepts/delegate-requirements/
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_TtyWjrv7xBaB7chEV6HLrg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Harness delegate installs fine but never connects: outbound 443 <span>— Vectle</span></a>