The proxy rejected your credentials. Re-enter the username and password exactly as issued, or supply them where the client expects them, and the 407 clears.

Proxy authentication errors

Fix 407 Proxy Authentication Required

Quick answer

A 407 status means the proxy understood the request but demands valid credentials before forwarding it. The target site was never contacted.

Exact error text
Likely causes ranked
Ordered diagnostics
Verified remedy

When this is the right fit

  • Exact error text
  • Likely causes ranked
  • Ordered diagnostics

Who this page is for

Fix 407 Proxy Authentication Required

A 407 status means the proxy understood the request but demands valid credentials before forwarding it. The target site was never contacted.

Diagnosis tree

407 on every request

Likely causes

  • - Username or password mistyped (trailing spaces, wrong case)
  • - Credentials supplied to the wrong layer (site auth instead of proxy auth)

Verified remedy

Re-copy both credentials from the dashboard. In most clients the proxy credential goes in the proxy URL or proxy-auth field, not the website's login.

407 in one tool, other tools work

Likely causes

  • - The tool does not answer proxy auth challenges automatically
  • - Special characters in the password are not URL-encoded in a proxy URL

Verified remedy

Use the client's dedicated proxy-authentication option, or URL-encode special characters in user:pass@host form. Test with curl -x http://user:pass@host:port https://api.ipify.org to separate proxy issues from client issues.

407 after credentials worked before

Likely causes

  • - Credentials were rotated (planned rotation)
  • - Endpoint was re-provisioned

Verified remedy

Pull the current credentials from the dashboard, update the client, and record the rotation date in your runbook.

Final connection check

  1. 1Confirm credentials in the dashboard
  2. 2Update the client with exact values
  3. 3Run one test request through the proxy
  4. 4Confirm the exit IP is the endpoint

Working connection

Requests return real responses (no 407) and the IP echo shows the endpoint.

Broken connection

A 407 after verified credentials means the client is not sending proxy auth at all: use its explicit proxy-authentication setting or a local forwarding tool that injects credentials.

Sources

Facts last reviewed 2026-09-01.

Prevent it recurring

Store credentials in a vault, not a spreadsheet, and rotate on a schedule your team documents. When rotation happens, update every client in the same maintenance window and note it in your runbook.

195+ countries
99.9% uptime guarantee
Unlimited bandwidth
4.9/5 from 127 ratings

Frequently asked questions

What does 407 Proxy Authentication Required mean?

The proxy wants valid credentials before forwarding your request. It is a proxy-layer rejection, not a website response.

How do I pass proxy credentials in a URL?

Use the scheme http://username:password@host:port and URL-encode special characters. If your tool has a dedicated proxy-auth field, prefer it.

Choose one stable proxy for every active profile

Buy self-serve now, or talk with us about a larger agency inventory.