Error message

Dedicated IP gateway error (HTTP 400)

Last updated 6 August 2026

Dedicated IP gateway error (HTTP 400 error page)

In short

This error means your request goes out through your account's dedicated IP, and that IP sent back an error page of its own instead of passing the request on. Because the request stopped at the IP, it never reached your broker — so this is not a broker outage, and it is not your broker login or API credentials. Nothing was sent to the broker, so no order was placed and there is nothing to cancel. This is almost always a short, temporary fault at the IP, and it clears on its own. Wait a few minutes and try again. You do not need to change any setting, password or API key. If it keeps happening, contact our support team — an IP fault is ours to chase, not something you can fix from your side.

When this happens

  1. 1 The dedicated IP had a temporary fault and answered with an error page instead of passing your request on.
  2. 2 The IP was briefly overloaded or being worked on, so it could not carry requests for a short time.
  3. 3 Your own IP (BYOIP) is having a problem at the vendor you bought it from.

What this error means

Your requests go out through a dedicated IP that belongs to your account. This error means that IP answered with an error page of its own instead of passing your request on to the broker.

The important part: the request 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 request.

No order was placed. Because the request was stopped before it reached the broker, there is no order sitting at your broker and nothing for you to cancel. It is safe to try again.

How this error can look

The clearest version of this message names your dedicated IP as the cause:

Dedicated IP gateway error (HTTP 400): the request went out through this account’s dedicated IP and the IP returned an error page instead of passing the request on, so it never reached Angel One.

Older messages for the same problem looked very different. They named your broker and mentioned reading or mapping a response, with a 400 Bad request web page in the text. For example:

Error from Angel One: [Parsing Failed] Failed to map response to OrderResponse … Body snippet: <html><body><h1>400 Bad request</h1>

That older wording was misleading — it named the broker for a request the broker never received. If you see a message like that and your account uses a dedicated IP, this article is the one you need, not the broker server error article.

A useful clue: if several of your accounts fail at the same moment, and they use different brokers, the problem is almost never the brokers. Something on the path they share — the dedicated IP — is at fault.

How to fix it

  1. Wait a few minutes and try again. These faults are usually short and clear up on their own. This fixes it in most cases.
  2. Do not change your settings. You do not need to change your broker login, API key, password or IP details. Nothing on your side caused this, so changing settings will not help and may cause a different problem later.
  3. If you use your own IP (BYOIP), check it with your vendor. Open Settings → My IPs, go to the Proxy pool tab and confirm the IP is still active and paid with the vendor you bought it from.
  4. If it keeps happening, contact us. Reach our support team with the account name and roughly when it happened. If the IP came from our pool, this one is ours to chase — you cannot fix it from your side.

Our team is alerted automatically when this affects many accounts at once, so a wider problem is usually already being looked at by the time you notice it.

How this is different from other IP errors

  • “Proxy Authentication Required” (407) — the IP answered and refused you, usually over a wrong username or password. There you do need to check your IP details. See Dedicated IP authentication failed.
  • “Connect timed out” / “Dedicated IP not reachable” — nothing answered on the IP at all. See Connect timed out to your own IP.
  • “Dedicated IP did not respond” — the request did go out and no reply came back, so the order may already be at your broker. That is the one case where you must check your order book before retrying. See Dedicated IP did not respond.
  • “Broker rejects your IP” — the request does reach the broker, and the broker blocks it because the IP is not on its whitelist. See Broker rejects your IP.
  • Broker server error — the request reaches the broker and the broker’s own system fails. See Broker server error.
Did this solve your problem?
Contact support