Customer Story: Fixing MT5 VPS Port Access with a Dedicated IP on an Express Windows VPS
An individual trader rented an Express Windows VPS to run MetaTrader 5 (MT5) on a server that stays online. The terminal opened and Remote Desktop (RDP) worked, but MT5 could not connect to their account at a retail forex broker. Support traced the problem to port access: a shared IP only opens a fixed list of VPS ports. A dedicated IP, at $2 per month, was added.
Submitted by user "n**@****.com" · Support ticket, April 18, 2026*
Application Scenario
The customer uses their MT5 VPS hosting for a simple, common job:
- Running one MT5 terminal on a Windows VPS that stays online
- Connecting the terminal to a personal account at a retail forex broker
- Reaching the server over RDP from their own computer
The server was running and the desktop was reachable. The terminal still could not log in to the broker, which is what they wrote to us about.
Server Specifications
Product Name: Express Windows VPS
CPU: 2 CPU Cores
RAM: 4GB
Storage: 60GB SSD
IP Address: 1 Shared IPv4
Operating System: Windows
Software: MetaTrader 5, RDP access
One terminal fits this size comfortably, so capacity had nothing to do with what happened next.
The server was up, but MT5 couldn't connect
At 22:12 on April 18, 2026, the customer opened a ticket with one question: why can't my server access my MT5 account? They mentioned which broker they used, which helped support look at the problem in context.
The original ticket as submitted by the customer.
What made it confusing is that everything else looked fine. RDP worked, Windows was running, and MT5 opened without complaint. The failure only appeared when the terminal tried to reach the broker, and the error doesn't say whether the server, the terminal or the broker is to blame. Port access is easy to overlook on an MT5 VPS because the desktop gives no hint about it.
What people usually try first
In this situation, most people go through the same list: retype the password and server name, reinstall MT5, suspect the broker, suspect the VPS. Each of those can eat an evening, and none of them touch the cause here. This customer wrote to support, which turned out to be the shorter route.
How support found the cause
Henry from our Support Department, a human support expert, looked at the setup and pointed to the IP. The Express plan comes with one shared IPv4 address, and a shared IP only opens a fixed set of VPS ports. MT5 can need specific ports, or a wider range of them, to talk to a broker's trade servers. If the ports it needs aren't among the open ones, the terminal can't connect, even though the VPS itself is perfectly healthy.
The fix was a dedicated IPv4 address, which isn't bound by the shared IP's port rules. A dedicated IP costs $2 per month. Henry recommended it and offered to walk the customer through ordering.
By 23:30 the customer had already requested one. Henry then confirmed it was provisioned and gave a few ways to check:
- Connect to the server with the new IP address on your RDP port.
- Open the IP section of the control panel and confirm the new address is assigned.
- Run a ping test to check connectivity.
- Write back if anything still doesn't work.
| Date and time (2026) | What happened |
|---|---|
| Apr 18, 22:12 | Customer submits the ticket |
| Before 23:30 | Henry replies with the diagnosis and recommends a dedicated IP |
| Apr 18, 23:30 | Customer says they've already requested a dedicated IP |
| After 23:30 | Henry confirms the dedicated IP is provisioned and explains how to verify it |
Before and after
| Before | After | |
|---|---|---|
| IP | 1 shared IPv4 | Dedicated IP added |
| Port access | Fixed set of VPS ports only | Not limited by shared IP port rules |
| Cause of the failure | Unknown | Identified, and the customer was already acting on it 78 minutes after opening the ticket |
| Added cost | None | $2 per month |
| MT5 connection to the broker | Failing | Successful |
The ticket stops at the point where the dedicated IP goes live, so we can't tell you how the reconnect went. If you follow the same steps, test the terminal as soon as the new IP is active and tell support what you see.
If MT5 can't reach your broker from a VPS, check which VPS ports your IP opens before you reinstall anything.
Add an IP later, or start with one
Express uses a shared IP, and a dedicated IP can be added for $2 a month. Windows VPS plans from Express Plus upward include a dedicated IP by default, so there's nothing extra to buy.
If your MT5 VPS hosting depends on specific VPS ports, say a broker connection that behaves like this one, a tunnel, or other trading tools, starting on Express Plus or above saves you the detour. If you're not sure, tell our team what you plan to run before you order, and we'll point you to the right option.
Notes & Troubleshooting
- A running VPS doesn't guarantee a working MT5 connection. If the terminal fails while the server looks healthy, check the IP and its port access first.
- After any network change, confirm the new IP in the control panel, ping it, then reconnect the terminal.
- If you rely on a broker connection, a tunnel or other tools that need specific VPS ports, tell support before you order.
- Technical support is available 24/7 by ticket and live chat, and every ticket is answered by a person. In this case that was Henry, and the timestamps above come from the ticket itself.
Deploy Your Own Version of This Use Case Now?
Express Windows VPS for MT5
- CPU: 2 CPU Cores
- Memory: 4GB RAM
- Disk: 60GB SSD
- IP: 1 Shared IPv4 (dedicated IP available for $2/mo)
- OS: Windows
$8.99/mo
Want MT5 VPS hosting with port access sorted out from the start? Windows VPS plans from Express Plus and above come with a dedicated IP by default. Running several terminals? See our Windows VPS sizing for MT5, or a dedicated server for 20 terminals or more.
Last Updated: 10/27/2026