Error message

Proxy Authentication Required (HTTP 407)

Last updated 16 July 2026

Dedicated IP authentication failed (Proxy Authentication Required / 407)

In short

This error means your order goes out through your account's dedicated IP, and that IP refused the connection with a "Proxy Authentication Required" (407) message. Because the connection was stopped at the IP, the order never reached your broker — so this is not a broker outage, and it is not your broker login or API credentials. It usually happens when you bring your own IP (BYOIP) and its username or password is saved wrongly, or the IP has expired or been paused by the vendor you bought it from. If you use your own IP, open Settings → My IPs, go to the Proxy pool tab, check that the IP host, username and password are correct and that the IP is still active with your vendor, then click Validate All and try again. If the IP was assigned from our pool, you cannot fix this yourself — contact our support and we will check it. An IP can start failing even if it validated fine earlier, if the vendor later changes or pauses it.

When this happens

  1. 1 You use your own IP (BYOIP) and its username or password is saved wrongly, so the IP refuses the connection.
  2. 2 Your bought IP, or its plan, has expired or was paused by the vendor you bought it from.
  3. 3 The IP is assigned from our pool and needs our team to check it.

What this error means

Your orders go out through a dedicated IP that belongs to your account. This error means the connection to that IP was refused with a “Proxy Authentication Required” (407) message.

The important part: the connection was stopped at the IP, before it ever reached your broker. So this is not a broker problem, and it is not your broker login or API credentials. Your broker never saw the order.

This is different from “broker rejects your IP”. There, the order does reach the broker, and the broker blocks it because the IP is not on its whitelist. Here, the order does not even get that far — the IP itself did not accept the connection.

An IP can start failing this way even if it validated fine before. If the vendor you bought the IP from later changes its password, pauses it, or the plan ends, the IP begins to refuse connections.

How this error can look

The message is not always worded as “Proxy Authentication Required”. Because the IP refuses the connection with a page our system cannot read, the same problem often reaches you while validating your account as a parsing or mapping error that names your broker and carries an HTTP 407 status. For example:

Error from Angel One: [Parsing Failed] Failed to map response to LoginResponse … [Status: 407]

Even when the text names a broker (for example “Error from Angel One”) or says “Parsing Failed” or “Failed to map response”, the 407 is the part that matters: the connection was stopped at your dedicated IP, and the broker never received the request. If you see 407 or Proxy Authentication Required anywhere in the message — while validating an account, logging in, or placing an order — this is the article you need.

How to fix it

If you use your own IP (BYOIP)

You added your own IP, so you can fix this yourself:

  1. Check with the vendor you bought the IP from that the IP is still active and paid. If it expired or was paused, renew it.
  2. In our system, open Settings → My IPs and go to the Proxy pool tab. Edit that IP there.
  3. Make sure the host, port, username and password match exactly what the vendor gave you. A changed or mistyped password is the most common cause.
  4. Click Validate All. If it passes, place the order again.

If the details look correct but it still fails, contact our support team and we will help you check it.

If your IP was assigned from our pool

You cannot fix this one yourself. Please contact our support team and tell them which account is affected. We will check the IP and set it right.

Did this solve your problem?
Contact support