407 - Proxy Authentication Required

Start Here

Use the closest compare guide, playbook, or adjacent error page to narrow the decision faster before you start changing production systems.

This page is part of the Error Reference library. Learn more about the project or report a correction.

What Does Proxy Authentication Required Mean?

A proxy in the request path is demanding authentication, so traffic is blocked before it can reach the target origin.

Common Causes

• -Outbound route passes through authenticated proxy, but client does not attach Proxy-Authorization credentials.
• -Proxy challenge requires NTLM or Kerberos scheme while client attempts Basic credentials for same route.
• -PAC or environment proxy settings route only some domains through restricted proxy realm, causing selective failures.

How to Fix Proxy Authentication Required

1. 1Inspect Proxy-Authenticate challenge and supply valid Proxy-Authorization credentials for the required scheme.
2. 2Verify client proxy settings and credential source are applied to the exact outbound route.
3. 3Retest through the same proxy path and confirm traffic reaches origin without additional proxy auth challenges.

Step-by-Step Diagnosis for Proxy Authentication Required

1. 1Capture proxy challenge headers and identify required auth scheme/realm.
2. 2Verify client runtime actually routes through the expected proxy and includes correct credentials.
3. 3Check credential expiry, encoding format, and policy scope at proxy controller.
4. 4Retest with controlled proxy credentials and validate origin receives the forwarded request.

curl -i -X GET https://api.example.com/v1/resource --proxy http://proxy.example.net:3128
# Response:
# HTTP/1.1 407 Proxy Authentication Required
# {"error":"Proxy Authentication Required","code":"407"}

const response = await fetch('https://api.example.com/v1/resource', {
  method: 'GET',
  headers: { 'Accept': 'application/json' }
});
if (response.status === 407) {
  console.error('Handle 407 Proxy Authentication Required');
}

import requests

response = requests.get(
    'https://api.example.com/v1/resource',
    headers={'Accept': 'application/json'}
)
if response.status_code == 407:
    print('Handle 407 Proxy Authentication Required')

Seen in Production

Debugging Tools

• -Proxy access/auth logs by client identity
• -PAC/proxy configuration inspection tools
• -curl through proxy with verbose headers
• -Credential vault and rotation audit logs

How to Verify the Fix

• -Re-run affected requests and confirm 407 disappears while origin responses are returned.
• -Validate proxy authentication remains stable across credential refresh cycles.
• -Monitor proxy auth failure metrics to ensure no recurring challenge loops.

How to Prevent Recurrence

• -Automate proxy credential rotation and expiration monitoring in all environments.
• -Standardize proxy configuration (PAC, env vars, credential injection) across clients and CI agents.
• -Add health checks that validate proxy auth handshake before production job execution.

Pro Tip

Related Errors

Official References

• -RFC 9110 Section 15.5.8 - 407 Proxy Authentication Required definition
• -IANA HTTP Status Code Registry - 407 Proxy Authentication Required
• -MDN Web Docs — 407 Proxy Authentication Required
• -HTTP Official Documentation