Skip to main content
Trader problem · VPN connection

Why Your VPN Keeps Blocking or Dropping the MT4 Connection

MT4 uses a persistent TCP connection with keepalive packets to stay linked to the broker's server. VPN clients frequently intercept, delay, or drop these keepalives — causing the connection to time out silently while the platform still shows Connected.

TL;DR

MT4's broker connection relies on TCP keepalive packets sent at regular intervals. Many VPN clients handle these packets poorly: they may drop them, delay them, or reset the connection when switching between VPN servers. The result is a connection that appears live in the MT4 status bar but is actually frozen — orders fail, ticks stop updating, and reconnects happen without warning.

See the plansMT4 disconnecting on VPS guide
30–60s
Interval of MT4 keepalive packets
Silent
MT4 still shows Connected during drop
Pure overhead
VPN interference has no benefit

How MT4 maintains its broker connection

MT4's connection to the broker's server is not a momentary query — it is a persistent TCP session that stays open for the entire trading session. This connection carries ticks (price updates), trade confirmations, and the live server time.

To keep this connection alive across the internet, both MT4 and the broker's server send periodic TCP keepalive packets. These are small, low-overhead messages that say, "I am still here, do not close the connection." Typically, MT4 sends a keepalive every 30–60 seconds.

If keepalives stop arriving on the broker's side, the server's TCP stack assumes MT4 has gone offline and closes the connection. If MT4 stops receiving keepalives from the broker, it detects the broken connection and triggers a reconnect. The keepalive mechanism is the glue that keeps the session stable across variable network conditions.

How VPN clients disrupt TCP keepalives

VPN clients create a virtual network interface on your computer. All traffic from MT4 — including keepalive packets — flows through this virtual interface instead of your physical network adapter.

When the VPN client renegotiates encryption keys (typically every 60–90 minutes), reconnects to a different server, or switches routing tables, the virtual interface can drop packets briefly. Those dropped packets may include MT4's critical keepalive packets.

The sequence looks like this:

  1. VPN client triggers a rekey or server reconnection.
  2. Virtual interface drops a packet — which happens to be MT4's keepalive.
  3. Broker waits for the next keepalive, does not receive it, and times out the connection.
  4. MT4's status bar still shows Connected because MT4 has not yet detected the timeout.
  5. Orders sent during this window fail with "Broker busy" or disappear from trade history.
  6. After 30–60 seconds, MT4 detects the broken connection and shows "Waiting for data."

Signs your VPN is breaking the MT4 connection

Watch for these symptoms when a VPN is active:

  • Frequent reconnect messages in Journal tab: Open the Journal tab in the Terminal window. If you see "Disconnected from server" or "Connection restored" messages appearing every 30–90 minutes without obvious cause, a VPN issue is likely.
  • Charts freeze momentarily then resume: Charts stop updating for 5–15 seconds, then resume. This indicates the connection was broken and reconnected.
  • Orders placed during a freeze vanish: You click Buy or Sell during what looks like normal operation, but the order never appears in your trade history. The connection was broken at that moment.
  • Server time in MT4 stops updating then jumps: The server time shown in the top-right of MT4 stays frozen for a few seconds, then suddenly jumps forward. This is a sign the connection was broken and the reconnect caught up.

For more details on diagnosing MT4 disconnections, see MT4 disconnecting on VPS guide.

Diagnosing VPN-caused MT4 disconnects

To confirm that a VPN is causing the problem, run this test:

  1. Disable your VPN entirely.
  2. Start MT4 and let it run for 30–60 minutes during an active trading session.
  3. Open the Journal tab and count how many reconnect events appear.
  4. Re-enable the VPN and run the same test again for 30–60 minutes.
  5. Compare the number of reconnect events. A large difference points to the VPN.

You can also check Windows event logs: open Event Viewer ? Applications and Services Logs ? Microsoft ? Windows ? VPN Provider. Connection drops will be logged here when the VPN client reconnects or loses service.

Why SOCKS5 does not have this problem

A SOCKS5 proxy like TradersProxy does not create a virtual network interface and does not renegotiate encryption keys. MT4's TCP connection to your broker flows through the SOCKS5 proxy as a normal, transparent TCP stream — the proxy passes all traffic, including keepalive packets, without interference or delay.

SOCKS5 is stateless at the application layer. It routes packets, it does not filter, delay, or rekey them. Your keepalive packets reach the broker reliably and on schedule. The connection stays stable for hours without reconnects.

For help finding the right TradersProxy node for your broker, see Latency by broker — find your optimal node. Setup instructions are at Configure MT4 for SOCKS5 on Windows.

Choosing a VPN protocol if you must use one

If you need VPN access for security reasons (trading on untrusted WiFi, bypassing a georestriction), some protocols are less disruptive to MT4:

  • IKEv2: Most graceful for connection stability. Handles re-key and server switches with minimal packet loss.
  • WireGuard: Fast and efficient, rekeying is brief. Better than OpenVPN for keepalive reliability.
  • OpenVPN (UDP): Renegotiates every 60 minutes and briefly drops traffic. The worst choice for MT4.
  • OpenVPN (TCP): Slower and more disruptive than UDP mode.
Execution Quality

No virtual interface. No keepalive drops.

TradersProxy uses SOCKS5, which passes TCP traffic transparently — including keepalives. Your MT4 connection stays alive and stable across the proxy without VPN-style interference.

Try it free for 7 days

If the route is the problem, a dedicated trading proxy is the fix at the infrastructure level — a relay node co-located near your broker's datacenter replaces the unstable public internet hops with a dedicated path. 7-day trial on Starter →

FAQ

In MT4, open the Journal tab in the Terminal window. Reconnect events appear as timestamped entries. If you see frequent reconnects without corresponding news events or network outages, the connection is being broken by something in your local network — often a VPN.

It will restore the connection temporarily but not prevent future drops. The root cause (VPN keepalive interference) will continue until you remove or reconfigure the VPN.

Some VPN clients have a 'split tunnelling' feature that lets you exclude specific apps. Excluding MT4 from the VPN tunnel will restore normal connectivity but you lose the 'protection' for that traffic. Split tunnelling is a reasonable middle ground if you need the VPN for other applications.

Yes. OpenVPN UDP mode renegotiates keys every 60 minutes and briefly drops traffic. WireGuard is better behaved. IKEv2 is generally the most MT4-friendly VPN protocol if you must use one, because it handles reconnects more gracefully.

This is a classic symptom. MT4 can show Connected while the actual TCP data session is frozen or broken. In the Experts tab, look for 'Trade context is busy' or 'Connection lost' messages. If they appear shortly after normal-looking operation, a connection drop is the cause.