Dedicated IP not reachable: nothing answered at this account's dedicated IP
Last updated 6 August 2026
Dedicated IP not reachable / Connect timed out to your own IP (BYOIP)
This error means the request went out through the IP you brought yourself (BYOIP), and nothing answered on that address and port, so it timed out. You may see it as 'Dedicated IP not reachable', or as an older 'Connect timed out' message that names your broker — both mean the same thing. The request never reached your broker, so this is not a broker outage and not your broker login or API details — even when the message names your broker. Nothing was sent to the broker, so no order was placed and it is safe to try again. The most common reason by far is that the saved IP is a static IP your internet provider gave you on a broadband or leased-line connection. That is only an address, with no proxy behind it, so nothing can answer and it cannot work here. The other reasons are a wrong port, a proxy your vendor has paused or that has expired, or a proxy machine that is switched off. Open Settings, then My IPs, then the Proxy pool tab, and check the host, port, username and password against what your proxy vendor gave you, then click Validate All. If the IP came from your internet provider, buy a dedicated static IPv4 proxy in an India location from a proxy vendor instead, or take a static IP from us.
When this happens
- 1 The saved IP is a static IP from your internet provider (broadband or leased line). It is only an address, with no proxy behind it, so nothing answers.
- 2 Your own static IP was entered in the Proxy Host field, instead of the connection address your vendor gave you. That often still connects, so it saves and validates without any warning, but it can take a much slower route and time out.
- 3 The port is wrong — or you were never given one, which means the IP is not a proxy at all.
- 4 Your proxy has expired, or the vendor you bought it from has paused it.
- 5 The proxy runs on a machine that is switched off, or its internet line or port forwarding is down.
What this error means
Your account’s requests go out through the IP attached to that account. This error means our system tried to reach that IP on the saved port, nothing answered, and the attempt gave up.
The important part: the request stopped at the IP, before it ever reached your broker. So this is not a broker outage, and it is not your broker login or API credentials. Your broker never saw the request — even though the message often names your broker.
It is also different from a 407 / “Proxy Authentication Required” error. There, the IP answered and refused the connection, usually over a wrong username or password. Here, nothing answered at all — see Dedicated IP authentication failed (407).
And it is different from “Dedicated IP did not respond”. There, the connection was made and the request went out, but no reply came back — so the order may already be at your broker and you must check your order book before trying again. Here, nothing answered at all, so nothing was sent and it is safe to retry. See Dedicated IP did not respond.
How this error looks
You usually see it while logging in or validating the account. The clearest version of the message names your dedicated IP as the cause:
Dedicated IP not reachable: nothing answered at this account’s dedicated IP (1.2.3.4), so the request never reached Angel One.
Older messages for the same problem named your broker instead, and could be wrapped in
technical text. The part that mattered was failed: Connect timed out and the address and port
in front of it:
Login failed: Error from your broker: Connect to 1.2.3.4:1080 failed: Connect timed out
That older wording was misleading — it named the broker for a request the broker never received. If you see either message, this is the article you need.
The most common cause: an internet provider’s static IP
Check this first, before anything else.
Bring-your-own IP means you give us a proxy — a host, a port, a username and a password — and our system sends that account’s broker requests through it. A static IP that your internet provider gave you on a broadband or leased-line connection is only an address. There is no proxy behind it, nothing is listening on any port, and so nothing can answer. It cannot work here, and no port number will fix it.
That is also why your provider never gave you a port. A proxy vendor always gives you the host, the port, the username and the password together.
Full explanation, and what to buy instead: Can I use my internet provider’s static IP?
How to fix it
If your IP came from a proxy vendor
- Check with the vendor that the proxy is still active and paid. If it has expired or was paused, renew it.
- Open Settings → My IPs and go to the Proxy pool tab. Edit that IP.
- Make sure the host, port, username and password match exactly what the vendor gave you. A wrong port is the usual reason for a timeout.
- Check you have the right address in Proxy Host. Your vendor usually gives you two different addresses: the one you connect to, and the static IP your broker sees. They are easy to mix up. The Proxy Host field needs the connection address — not your own static IP. Putting your static IP there often still connects, so nothing warns you, but it can take a much slower route and time out on and off.
- If your vendor gave you a hostname, use the hostname, not the IP address it points to. Both work today, but vendors move a hostname to a different server when they need to, and only the hostname keeps working when they do.
- Click Validate All. If it passes, try logging in again.
If the details are right and it still times out, ask your vendor whether the proxy is reachable from outside their own network. Some vendors lock a proxy to one customer address until you turn on username and password login.
If your IP came from your internet provider
Nothing in our system can make that address work, so change the IP:
- Buy a dedicated static IPv4 proxy in an India location from a well-known proxy vendor, and save that in Settings → My IPs → Proxy pool instead. The Static IP Setup guide lists sample vendors and what to look for.
- Or take a static IP from us and skip the setup. Open the account’s card in Settings → My IPs and pick a static IP from us. Only one IP source can be active at a time, so this removes your own IP from the account, and you register the new address with your broker once. Prices are in Static IP for broker API trading.
If the IP was assigned from our pool
You cannot fix this one yourself. Contact our support team and tell them which account is affected. We will check the IP and set it right.
Related help
- Can I use my internet provider’s static IP (Airtel, Jio, BSNL)? — why a broadband static IP cannot be a bring-your-own IP.
- Dedicated IP authentication failed (407) — the IP answered but refused the connection.
- Dedicated IP did not respond — the request went out but no reply came back; check your order book before retrying.
- Static IP for broker API trading — every static IP option and its price.
- Broker rejects your IP (static IP not registered) — a different problem: the IP works, but the broker has not whitelisted it.