Agent cannot reach Datadog through a corporate proxy: set proxy config

TL;DR

Set the proxy in datadog.yaml (host) or the equivalent env vars (containers): - proxy.http / proxy.https: the proxy URL. - proxy.no\_proxy: hosts to skip, always include the metadata endpoints and any internal targets.

Steps

1. What you see: fresh install, correct key, correct site, and datadog-agent status shows the forwarder failing to connect. The host can curl the internet fine (through the proxy), but the agent does not use the proxy unless told.
2. Set the proxy in datadog.yaml (host) or the equivalent env vars (containers):
3. - proxy.http / proxy.https: the proxy URL.

• proxy.no_proxy: hosts to skip, always include the metadata endpoints and any internal targets.

4. Restart the agent. The forwarder should start accepting payloads.
5. Setting HTTP_PROXY on the host and assuming the agent picks it up. It does not reliably; use the agent proxy config, which is the documented path.

When to use

You are seeing this: The forwarder should start accepting payloads. Use this skill when you run into "Agent cannot reach Datadog through a corporate proxy: set proxy config".

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

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

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

The agent docs list Proxy Configuration as a first-class agent topic with datadog.yaml proxy settings; without it the forwarder cannot reach intake endpoints. Verified against live docs 2026-09-26.