Your platform already has a proxy field built in. MT4, MT5, cTrader, TradingView Desktop — all of them. You just need to know where it is and what to type.
Four fields from your portal. Paste them in. Done.
Don't have a plan yet? See the plans →
TL;DR
Before you start, you need three things: a TradersProxy account, your credentials from the portal (host, port, username, password), and your trading platform already installed. Log in to the portal, open Active Routes, and copy those four values before you touch the platform.
Setup time by platform: MT4 and MT5 take about three minutes. cTrader, TradingView Desktop, Sierra Chart, Optuma, and Telegram each take two to four minutes. NinjaTrader and Thinkorswim take five to ten minutes because they require a per-app proxy tool or JVM flags rather than a built-in proxy field.
The guides below show the exact menu path for each app. Choose SOCKS5 where both protocols are available. If your platform has no native proxy field, use Proxifier or Sockscap64 and route only that executable through the relay.
In this guide
Every platform below asks for four things. They may call them different names. The values are always the same four pieces.
Host. The proxy server address. A domain name — something like relay.tradersproxy.com or an IP address. Copy it exactly from your portal.
Port. A number. Your portal shows the SOCKS5 port and the HTTP port separately. Use the one that matches the protocol your platform supports. If it supports both, choose SOCKS5.
Username. Your proxy credential username. Not your portal login email. The proxy username is shown in the Active Routes panel.
Password. The proxy credential password. Also in Active Routes. Copy it — don't type it. One wrong character causes a silent timeout.
That's it. Four fields. Find them in the portal before you touch the platform.
Keep the portal open while you work. If you still need access, see the plans ->
Each card links to a dedicated walkthrough with the exact menu path for that platform.
Tools → Options → Server
MetaTrader 5 MT5 proxy configurationTools → Options → Server
cTrader cTrader proxy setupSettings → Advanced → Connection
NinjaTrader 8 NinjaTrader proxyVia per-app proxy tool
TradingView Desktop TradingView proxySettings → Network
Sierra Chart Sierra Chart SOCKS5Login window → Proxy Settings
Thinkorswim (TD/Schwab) Thinkorswim proxySettings → General or JVM flags
Optuma Optuma proxy setupLogin screen → Server Settings
Telegram  & Pro plans Telegram MTProto setupSettings → Data and Storage → Proxy
MT4 has a proxy field in the Server tab of its Options dialog. It supports SOCKS4, SOCKS5, and HTTP. Use SOCKS5 unless your broker's server explicitly requires HTTP.
After relaunch, look at the bottom-right corner of the MT4 window. The signal bar indicator shows the connection status. Green bars mean MT4 is connected to your broker through the proxy. If you see a grey bar or a red X, the proxy details are wrong — go back to the Proxy… dialog and verify the host and port match your portal exactly.
Login fails on the Test button. Double-check the username and password. Re-copy them from the portal. One wrong character causes a silent auth failure.
Port 443 appears blocked upstream. Some ISPs and corporate networks block non-standard outbound ports. Your portal shows an alternate port — try it. If both ports time out, your network is blocking outbound TCP on those ports. Try on a different network (mobile hotspot) to isolate the issue.
Test passes but MT4 still shows "No connection" after restart. The proxy test succeeds even if the broker's server address itself is unreachable. Confirm your broker login (server, account number, password) is correct separately from the proxy setting.
MT5's proxy setting lives in the same place as MT4 — Tools → Options → Server tab. The dialog is nearly identical. Two differences: MT5 shows a ping value in the status bar, and MT5 supports NTLM authentication in HTTP mode. Use SOCKS5 unless your broker requires NTLM. SOCKS5 has no per-packet auth overhead.
Look at the bottom status bar of MT5. The connection indicator shows green bars when connected. Hover over it to see the ping value to your broker. A value under 100 ms means the route is working. If you see "No connection", verify the port number matches your portal exactly — MT5's error messages do not distinguish between a wrong port and a wrong password.
NTLM auth option appears. This is for HTTP proxy mode on certain corporate broker setups. If you see it, you are not in SOCKS5 mode. Change the type to SOCKS5 first.
Multiple MT5 terminals, each with a different broker. Each instance has its own proxy settings. Configure each terminal separately using the same portal credentials.
cTrader's proxy setting is in the Advanced section of its Settings panel. It supports both HTTP and SOCKS5. There is also a separate toggle that controls whether price feed (market data) routes through the proxy alongside order traffic. Enable both.
cTrader shows "Disconnected" immediately after Apply. Restart first. Some versions do not apply the change until the app is relaunched.
Switching between SOCKS5 and HTTP. Some broker configurations only allow one protocol. If SOCKS5 fails after correct credentials, switch to HTTP. The host and port are the same — the proxy accepts both protocols on the same address.
NinjaTrader 8 does not have a built-in proxy settings panel in the main application. You route it through TradersProxy using a per-app proxy tool that intercepts NinjaTrader's outbound TCP before it leaves your machine and forwards it through the SOCKS5 proxy.
Proxifier is a paid Windows and macOS tool that routes specific executables through a proxy without touching the rest of the system.
NinjaTrader.exe. Set the Action to route through the proxy you just added.NinjaTrader.exe and routes it through the proxy. Your NinjaTrader data feed and order routing go through TradersProxy. The rest of your machine is unaffected.Some NinjaTrader data providers expose proxy fields in their own connection dialog. Rithmic, CQG, and Interactive Brokers each have separate connection setup screens. If you see proxy fields there, enter your TradersProxy SOCKS5 details directly — no per-app proxy tool needed for that data connection.
Setting a system-wide SOCKS5 proxy in Windows Settings → Network → Proxy routes all traffic from the entire machine through the proxy — not just NinjaTrader. Use this only if per-app tools are not available. It changes the network behavior of every app on the machine.
TradingView Desktop has a proxy settings panel. The web app (browser version) does not — it uses whatever network the browser uses. If you need proxy routing for TradingView, use the desktop app.
The web app at tradingview.com has no in-app proxy setting. The browser routes all tabs through whatever the OS or browser is configured to use. Options:
The core TradersProxy use case — clean routing for your trading terminal — does not require routing web traffic. Route the trading app. Leave the browser alone.
Sierra Chart has a SOCKS5 proxy option in its login dialog. When configured, all Sierra Chart connectivity — data feed and order routing — runs through the proxy. This gives full, clean coverage for the platform.
TransAct and Rithmic connections in Sierra Chart do not route through Sierra Chart's own proxy setting. They use their own connection layer. If you use CQG, Trading Technologies, or Interactive Brokers as your data/routing provider in Sierra Chart, those connections route through the SOCKS5 proxy as expected.
Thinkorswim (available via TD Ameritrade and Schwab) has proxy support through two paths: an in-app settings panel, and JVM startup flags for advanced configuration. Try the in-app method first.
Thinkorswim runs on Java. You can pass SOCKS5 proxy settings as Java system properties at startup. Find thinkorswim.vmoptions in your Thinkorswim installation directory and add these lines:
-DsocksProxyHost=YOUR_PROXY_HOST
-DsocksProxyPort=YOUR_PROXY_PORT
-DproxySet=trueReplace YOUR_PROXY_HOST and YOUR_PROXY_PORT with the values from your portal. This routes all Thinkorswim traffic through the SOCKS5 lane. Restart Thinkorswim after saving the file.
Optuma exposes its proxy settings on the login screen before the application loads. The configuration is straightforward: one checkbox, four fields.
Optuma uses port 80 for data feed and port 5222 for live chat features. TradersProxy handles these automatically — you do not need to enter separate ports per service.
Troubleshooting. If Optuma hangs on login after configuring the proxy, double-check the host, port, username, and password in the portal. Credentials are case-sensitive. If the hang persists, restart Optuma and re-enter the credentials rather than editing in place.
Telegram MTProto proxy support is available on Standard and Pro plans. Starter plan includes SOCKS5 routing for Telegram, but not MTProto.
MTProto is Telegram's own proxy protocol. It is designed to work even when standard SOCKS5 connections are detected and blocked by network-level filters. For signal traders in restricted regions, MTProto keeps Telegram reachable when SOCKS5 does not.
Your portal generates a deep-link for your MTProto credentials. Tapping the link on a device with Telegram installed opens Telegram directly to the Add Proxy screen, with the server, port, and secret pre-filled. The link format is:
Copy the link from your portal's Active Routes panel (available on Standard and Pro plans). Open it on your phone to install the proxy in one tap. The implementation uses FakeTLS and MTProto to ensure the connection is not distinguishable from regular HTTPS traffic at the network level.
This guide is the setup reference. If you still need credentials, the plans page is where access starts. See the plans ->
These are the three mistakes most people make. Avoid them and you're done in five minutes.
Your portal shows a SOCKS5 port and an HTTP port. They are different numbers. MT4 and MT5 default to SOCKS5 — use the SOCKS5 port. If you configure HTTP mode and paste the SOCKS5 port, the connection fails silently: no error, just a timeout.
Fix: open your portal, look at Active Routes, and confirm you're using the port labelled for the protocol you selected in the platform.
If you manage multiple accounts — or if you set up TradersProxy on behalf of someone else — it's easy to paste credentials from the wrong portal session. The proxy rejects them with an auth error, but MT4 and MT5 show it as a generic "No connection".
Fix: log in fresh to the portal, navigate to Active Routes, and copy-paste. Don't use saved clipboard values from an earlier session.
Corporate networks, some ISPs, and certain antivirus products block outbound TCP on non-standard ports. The proxy is unreachable before the platform even attempts auth. MT4 shows "No connection". A successful Test in the proxy dialog confirms the port is open.
Diagnose: try connecting on a mobile hotspot. If it works there, the issue is your local network. Your portal's alternate port may be available on port 443, which most firewalls allow.
The proxy is connected. The platform's indicator is green. Quotes are frozen. Orders time out. Here's the diagnostic sequence.
Firewall or antivirus interrupting the session. Some security tools allow the initial TCP handshake but drop subsequent packets. Temporarily disable the firewall and test. If quotes resume, add the trading platform's executable to your firewall's allow list and re-enable.
ISP shaping or throttling. Some ISPs treat SOCKS5 connections as peer-to-peer traffic and throttle them after the first few seconds. Symptoms: connection succeeds, then freezes after 10–30 seconds. Test on a mobile hotspot. If quotes flow normally on LTE, the issue is ISP-side. The alternate port in your portal (typically on 443) often bypasses this.
Platform not fully restarted. MT4 and MT5 sometimes hold an old connection open after a proxy change. Fully quit the app — right-click the tray icon, choose Exit — and relaunch. Closing the main window does not close the terminal process on all systems.
Portal status page. Log in to the portal and check the node status for your account. If your assigned node is degraded, the portal shows it. A node failover to your backup node is automatic, but takes up to 60 seconds to propagate.
Bandwidth quota. If your account has consumed its hard cap for the current billing cycle, new connections are paused. The portal shows your current usage. Hard cap values: Starter 4 GB, Standard 10 GB, Pro 20 GB, Founder 50 no hard cap.
If the portal status shows the node healthy, your quota is not exhausted, and the mobile hotspot test shows the same behaviour, re-copy the credentials from the portal, restart the platform fully, and test on a second network before assuming the relay is the problem. This product is designed to be self-serve, so the diagnostic path needs to stand on its own.
This page is the reference. The portal is where your live credentials sit. Use both together and you will be connected in a few minutes.