Does Amibroker support SOCKS5 in AFL?

Not as a first-class AFL keyword. Use HTTP CONNECT on 443, or a local helper that speaks SOCKS5 to Algo-IP.

Static IP for Amibroker AFL — HTTP Through a Dedicated Indian IP

Route Amibroker AFL Internet / plugin HTTP calls through a dedicated Mumbai static IP on port 443 so Indian broker or webhook endpoints see one whitelist address.

When Amibroker needs a static IP

If AFL only paints charts from a local database, you do not need a whitelist. If AFL, IBController-style plugins, or an external DLL place orders on Zerodha, Dhan or a webhook listener that checks origin — the Windows box must egress through a dedicated IP.

Windows proxy for the Amibroker process

Amibroker’s Internet* AFL functions follow WinHTTP / WinINet settings. Set a per-user HTTP proxy to HOST:443 with the dashboard username and password, or run a tiny local forwarder and point AFL at 127.0.0.1. Do not put 8088 in the dialog on Jio home broadband.

Pattern that works

Whitelist the Algo-IP IPv4 on the broker or webhook allow-list.
Configure Windows or the plugin proxy to HTTP CONNECT 443.
From AFL, hit a known echo URL once and log the returned IP before the first live order.
Keep charting data local; only order HTTP should use the proxy if you want to limit bandwidth.

If you already have a Node or Python bridge, put the static IP on the bridge (see the Node.js guide) and keep Amibroker as the signal engine.