---
title: Troubleshoot the eBPF proxy
source: https://docs.newrelic.com/docs/ebpf/troubleshooting/proxy
---

If the New Relic eBPF agent isn't routing telemetry through your proxy as expected, use this page to diagnose common errors. For setup instructions and configuration reference, see [Configure a proxy for the New Relic eBPF agent](https://docs.newrelic.com/docs/ebpf/proxy-configuration).

## Common errors [#common-errors]

**HTTP proxy returned response code 400**

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

**Solution:** Use a `CONNECT`-capable proxy. See [Supported proxy servers](https://docs.newrelic.com/docs/ebpf/proxy-configuration#supported-proxies).

**'https' scheme not supported in proxy URI**

**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.

**Socket closed or connection refused**

**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](https://docs.newrelic.com/docs/ebpf/proxy-configuration#test-connectivity).

**Proxy CONNECT aborted**

**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.

**Proxy configuration ignored: gRPC HTTP CONNECT proxy requires TLS**

**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.

**Proxy username contains special or uppercase characters**

**Problem:** Your proxy username or password contains characters that gRPC's URI parser doesn't accept. See [Credential character limitations](https://docs.newrelic.com/docs/ebpf/proxy-configuration#credential-limitations).

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