Troubleshoot the eBPF proxy

Problem: The proxy doesn't support the HTTP CONNECT method.

Solution: Use a CONNECT-capable proxy. See Supported proxy servers.

Problem: gRPC doesn't support https:// as a proxy scheme. This is a gRPC limitation, not an agent restriction.

Solution: Set the proxy scheme to http (for example, otlpProxy.scheme: "http"). Your telemetry data still travels TLS-encrypted end-to-end through the proxy tunnel. Only the connection to the proxy itself is plaintext.

Problem: The proxy server isn't running, or the host or port is incorrect.

Solution: Verify that the proxy is reachable using the curl test command.

Problem: The proxy rejected the CONNECT request because of a firewall rule, ACL, or unsupported destination.

Solution: Check your proxy server logs and confirm that CONNECT requests to port 443 are permitted from the agent's source IP.

Problem: A proxy is configured but TLS is disabled (for example, TLS_ENABLED=false). gRPC's HTTP CONNECT proxy implementation only works when the connection to the OTLP endpoint uses TLS.

Solution: Make sure TLS is enabled (it's enabled by default). The agent will then use the configured proxy.

Problem: Your proxy username or password contains characters that gRPC's URI parser doesn't accept. See Credential character limitations.

Solution: Use a proxy account with a lowercase alphanumeric username and a password that uses only letters, digits, and the allowed special characters.