When enabling log forwarding in an environment that has a proxy configured, logs aren't received by the log destination.
- Terraform Enterprise, v202203-1 and later
NO_PROXYdoesn't contain a matching hostname entry for the log destination
NO_PROXYcontains a partial hostname match for the log destination
To determine if the log forwarder is connecting successfully to the configured destination, check the log forwarding logs by connecting to the TFE host and running:
docker logs tfe-fluent-bit.
Connections that aren't successfully bypassing the proxy may produce errors similar to this:
2022-05-26T11:11:01.641380000Z [2022/05/26 11:11:01] [error] flb_establish_proxy error: ... Proxy response payload, usually an HTML error page ... 2022-05-26T11:11:01.709437000Z [2022/05/26 11:11:01] [ warn] [engine] failed to flush chunk '1-1653563460.253488461.flb', retry in 10 seconds: task_id=0, input=systemd.0 > output=splunk.0 (out_id=0)
Add the fully-qualified domain name for the destination to
- Restart the application
Logs are successfully forwarded to the configured destination and the
tfe-fluent-bit container no longer logs any errors.