---
title: Configure proxy settings for Elastic Agent components
description: Configuration of the {{agent}}'s proxy settings.
url: https://www.elastic.co/elastic/docs-builder/docs/3776/reference/edot-collector/config/proxy
products:
  - Elastic Agent
  - Elastic Agent
  - Elastic Cloud Serverless
  - Elastic Observability
applies_to:
  - Serverless Observability projects: Generally available
  - Elastic Stack: Generally available
  - Elastic Agent: Generally available
---

# Configure proxy settings for Elastic Agent components
When running the Elastic Agent in environments that require outbound traffic to go through a proxy, you must explicitly configure proxy settings.
You may need to configure a proxy if:
- Your app is deployed behind a corporate proxy or firewall.
- Your telemetry is sent to Elastic APM in Elastic Cloud or another hosted destination.
- Network errors such as `Connection timed out` or `SSL handshake failed` appear in logs.


## Available proxy variables


| Variable    | Description                                |
|-------------|--------------------------------------------|
| HTTP_PROXY  | URL of the proxy server for HTTP requests  |
| HTTPS_PROXY | URL of the proxy server for HTTPS requests |
| NO_PROXY    | Comma-separated list of hosts to exclude   |


## Configure proxy settings for the Elastic Agent

Most Elastic Agent components honor common proxy environment variables. The following examples show how to configure them:
<tab-set>
  <tab-item title="Docker run">
    ```bash
    docker run -e HTTP_PROXY=http://<proxy.address>:<port> \
               -e HTTPS_PROXY=http://<proxy.address>:<port> \
    	        otel/opentelemetry-collector:latest
    ```
  </tab-item>

  <tab-item title="Docker compose">
    ```yaml
    services:
       edotcollector:
          environment:
             - HTTP_PROXY=http://<proxy.address>:<port>
             - HTTPS_PROXY=http://<proxy.address>:<port>
    ```
  </tab-item>

  <tab-item title="Kubernetes pod manifest">
    ```yaml
    env:
       - name: HTTP_PROXY
         value: '<proxy.address>:<port>'
       - name: HTTPS_PROXY
         value: '<proxy.address>:<port>'
    ```
  </tab-item>

  <tab-item title="systemmd [Service] unit file">
    ```
    [Service]
    Environment="HTTP_PROXY=http://<proxy.address>:<port>"
    Environment="HTTPS_PROXY=http://<proxy.address>:<port>"
    Environment="NO_PROXY=<address1>,<address2>"
    ```
  </tab-item>
</tab-set>

<note>
  For the Elastic Agent, proxy support applies to all exporters, including those using gRPC. No special configuration is needed beyond the environment variables.If you're using an SDK that doesn't support proxy variables directly, consider routing telemetry through the Elastic Agent configured with proxy settings. This ensures consistent proxy handling. For more information, refer to [Proxy settings for EDOT SDKs](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3776/troubleshoot/ingest/opentelemetry/edot-sdks/proxy).
</note>


## Resources

[Proxy support - contrib documentation](https://opentelemetry.io/docs/collector/configuration/#proxy-support)