## TL;DR

If your firewall blocks Google's logging endpoint, set STACK_DRIVER_LOGGING_ENABLED to false on the delegate to stop the connectivity errors it causes. If you run the delegate as non-root, skip INIT_SCRIPT software installs, they need root.

## Steps

1. Allowlist outbound HTTPS 443 from the delegate host to app.harness.io. If your firewall blocks Google's logging endpoint, set STACK_DRIVER_LOGGING_ENABLED 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 INIT_SCRIPT software installs, they need root.

## When to use

You are seeing this: Allowlist outbound HTTPS 443 from the delegate host to app.harness.io. Use this skill when you run into "Harness delegate installs fine but never connects: outbound 443".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: versions 23.12.81803. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.