HTTP 407 means the proxy requires authentication for the request. Start with the proxy endpoint, the authentication method it expects, and the credentials issued for that endpoint. Changing the target website’s password does not correct a proxy-authentication failure.
This focused guide is for a confirmed HTTP 407 response. For errors without an HTTP response, begin with the general proxy diagnostic guide.
Keep the evidence: record the status, time, client application and proxy scheme. Keep passwords and authorization headers out of screenshots. A useful report identifies which connection failed without exposing access to the order.
RFC 9110, section 15.5.8 defines 407 and its relationship to proxy authentication. A 407 response includes a Proxy-Authenticate challenge. Do not treat every message containing “authentication” as equivalent: a target website login and a proxy challenge concern different services.
Write down the exact status rather than a paraphrase such as “access denied.” If your application hides the response behind a generic dialog, obtain a sanitized diagnostic from that application. Avoid repeatedly changing settings before you have recorded the original symptom.
Compare the host and port with the current order details. Then compare the selected proxy protocol. A set of credentials issued for one endpoint should not be assumed to authenticate at a different hostname, port or product.
Check whether the order expects a username and password or another supported access method. If it uses a source-IP allowlist, ask which public source address should be allowed. Do not add arbitrary addresses as a workaround. A VPN or a different internet connection can change the source address the proxy sees.
Copy the username and password into the fields intended for proxy authentication. Look for leading spaces, trailing line breaks and values copied from an old order. Some applications accept a complete proxy URL, while others have separate fields.
When a client accepts credentials inside a URL, special characters require appropriate URL-component encoding. When it has separate fields, follow that client’s documentation rather than applying URL encoding indiscriminately. Double-encoding a password can create another mismatch.
A small private checklist helps:
| Field | Compare with |
|---|---|
| Host and port | Current issued endpoint |
| Protocol | Supported endpoint and client settings |
| Username | Exact current order value |
| Password | Exact value, without whitespace added during copying |
| Access method | Credentials or an explicitly supported alternative |
After correcting one field, repeat a single request to a diagnostic endpoint you control or trust. Keep the destination and application unchanged. If the result changes, record which field changed rather than making several more adjustments immediately.
If another supported client works with the same endpoint, compare the failing client’s proxy-authentication configuration. If both fail with the same 407, prepare an order-specific support report. The proxy checking walkthrough explains how to separate endpoint connectivity from a target-specific response.
A timeout does not confirm an authentication rejection. A connection refusal can occur before an HTTP challenge is exchanged. A target website’s login page is also not a 407 merely because it asks you to sign in.
Keep the response, the network stage and the application behaviour separate. This avoids spending time changing a password when the client is actually trying to reach the wrong port.
Not when the failure is the proxy’s authentication challenge. Use the proxy’s issued credentials in the appropriate client fields.
Repeated identical requests provide little new diagnostic information. Check the configuration, make one controlled attempt, then report the sanitized result if it persists.
Send the order number, endpoint label, time, application and exact status. Share no password in a public conversation. Open the Proxyca bot to find your order details and available help.