MarinShort answer: Setting up a trading VPS means connecting securely through Remote Desktop, hardening the server before anything else goes on it, installing your broker’s MetaTrader build, transferring your expert advisors into the correct folder, enabling algorithmic trading, and configuring the platform to relaunch automatically after a reboot. The final step, which most guides skip entirely, is to restart the server and confirm that the platform, the account connection, and every robot recover without you touching anything. This walkthrough follows a setup I performed on a Dipgate Windows server with BlackBull Markets, and I flag which steps are specific to that provider and which apply anywhere.
Plenty of traders skip hosting because they assume configuring a remote server is a technical project. It is not. There is one genuinely fiddly moment during login, one security decision people rush past, and one step almost everyone forgets.
Why I Bothered Writing This Down
We run a lot of accounts at Algo Trading Space, and hosting sits underneath all of them. Over the years the same questions keep arriving: which username do I use, why does Remote Desktop reject my password, why did my robots stop trading after the server restarted.
None of those are advanced problems. They are undocumented ones, because most tutorials show the happy path and skip the parts where people actually get stuck.
So this guide follows a real setup, start to finish, on a $500 live account running two gold scalpers. Where something tripped me up, I say so. Where I made a choice you might reasonably make differently, I say that too.
What You Need Before Starting
Gather these first and the whole thing goes quickly:
- Your VPS welcome email. It contains the server IP address and the temporary password. Check spam or promotions if it has not arrived; providers commonly report it landing there.
- Your broker’s MetaTrader download link. Use the build from your own broker rather than a generic installer, since the server list comes preconfigured.
- Trading account number, password, and server name. Live or demo.
- Your EA files, already downloaded to your local machine.
- A password manager, or somewhere secure that is not a browser, to store the credentials you are about to create.
One note on timing. A newly ordered server may need several minutes before Windows finishes installing, so if the connection refuses immediately after purchase, wait rather than assuming something broke.
Secure the VPS Before Installing MetaTrader
- Confirm the server address and provider identity. Compare the IP in your email against your provider’s client area before connecting to anything.
- Change the temporary Administrator password immediately after your first login. Providers generate these automatically, and the original arrives in plain text by email.
- Use a long, unique password that appears nowhere else. Not a variation of your broker password.
- Install pending Windows security updates before you fund the account, not after.
- Enable whatever access controls the provider offers: firewall rules, IP allowlisting, a VPN or RDP gateway, or multifactor authentication.
- Switch off redirection you do not need. Clipboard, local drives, printers, and device redirection all widen the surface between your machine and the server.
- Do not save broker or server credentials in the browser on the VPS.
- Keep administrator access to people who actually maintain the machine. If nobody else needs it, nobody else gets it.
- Resist installing unrelated software. A trading server should run trading software and very little else.
I will admit I have been lazier about this in the past than I should have been. The reasoning that talked me out of it, that a small account is not worth attacking, is wrong: automated scanning does not check your balance first.
Step 1: Connect Through Remote Desktop
A VPS, short for Virtual Private Server, is essentially your Windows computer living in the cloud. You reach it the same way you would reach any remote Windows machine, using Microsoft’s Remote Desktop client or the newer Windows App (Microsoft documentation).
- Open the login email and copy the VPS IP address.
- Find the Remote Desktop application on your Windows computer.
- Paste the IP address into the field.
- Click Show More Options, then Connect.
Here comes the part that catches people. Windows automatically appends your local username to the login field, so it tries to sign in as the wrong user and fails.
Click More Choices, then select Different Account. Type the username for the server, which in my case was Administrator. Enter the password from the email and tick Remember Me so Windows Credentials Manager stores it, then click OK. Storing it means you can reconnect later without copying the password across every session, which you will otherwise be doing several times a week.
About That Certificate Warning
The warning frequently appears because the server uses a self-signed certificate, which is normal for a fresh VPS. It can also mean you have connected to the wrong address, or that the remote identity genuinely cannot be authenticated.
So before continuing:
- Confirm the IP address matches the one your provider supplied, character for character
- If your provider publishes a certificate fingerprint or verification procedure, compare it
- Do not continue if the address is unfamiliar, or if the warning appears on a server you have already connected to before
Accepting an unexpected certificate warning on a machine holding trading credentials is not a small thing. Check first, then proceed.
You should now be looking at a Windows desktop that behaves exactly like a local one.
Step 2: Read the Notepad File Before You Close It
The moment I logged in, a Notepad window appeared explaining that any platform shortcut placed in the My Platforms Autostart folder will launch automatically when the server restarts.
That folder is a Dipgate convenience, not a standard Windows feature, and I cover the provider-neutral equivalents in Step 7. Either way, note it now rather than closing the window and forgetting, as I very nearly did.
Step 3: Install MetaTrader on the Server
Open a browser on the VPS and go to your broker’s download page.
I used Microsoft Edge because it came preinstalled on this server. Whichever browser you use, close it once the download finishes so its tabs and background processes stop consuming memory you would rather give to charts and robots.
For this setup I chose BlackBull Markets, mainly because they support MetaTrader 5, which is my preferred platform.
Download the Windows installer and run it. The installer offers a chance to change the installation directory; I left it at the default. Wherever you put it, note the path, because Step 7 needs it.
Click Finish when installation completes and the platform opens by itself.
Step 4: Log Into Your Trading Account
The broker’s server appears automatically in the connection dialog.
- Click Next
- Enter your trading account number and password
- Select the correct server, in my case BlackBull Markets Live
- Click Finish
Connected. Mine was a $500 account, small on purpose, since I would rather test infrastructure on capital I can afford to lose than on the account that matters.
Double-check the server field before finishing. Selecting a demo server when you meant live, or the reverse, is a mistake that stays invisible until trades either fail to appear or appear where you did not want them.
Once connected, close the default panels you are not going to use. MetaTrader opens several by habit, and each one costs memory it has not earned.
Step 5: Prepare Your Charts
I was running two gold scalpers, so I opened two gold charts. Everything else got closed.
Right-click in Market Watch and choose Hide All to remove symbols you are not trading. Unused charts and streaming symbols consume memory continuously, and on a server sized for trading rather than gaming that matters more than most people realize.
This housekeeping feels optional right up until the terminal lags during a busy session.
Step 6: Install Your Expert Advisors
Copy the EA files from your local machine. Mine were on my desktop: the MeetAlgo Global Trade Plan and the MeetAlgo Prime Scalper.
Then, inside the platform on the VPS:
- Click File, then Open Data Folder (MetaTrader help)
- Open the MQL folder for your platform, then Experts
- Paste the files there
- Return to the Navigator panel, right-click Expert Advisors, and select Refresh
Refresh is the step people miss. Without it the files sit in the right folder while the platform pretends they do not exist, which produces a fair amount of unnecessary panic.
MT4 and MT5 Differ Here
| Platform | EA folder | Compiled file | Toolbar button |
| MetaTrader 4 | MQL4 then Experts | .ex4 | AutoTrading |
| MetaTrader 5 | MQL5 then Experts | .ex5 | Algo Trading |
Source files ending in .mq4 or .mq5 need compiling in MetaEditor before the platform will recognize them. If a robot fails to appear after a Refresh, an uncompiled source file is a common reason.
Both of my robots default to the H1 timeframe, worth checking for your own systems before attaching anything. Drag each EA onto its chart and click OK. In the settings window, allow live trading, and grant DLL or WebRequest permissions only when the vendor genuinely requires them and you trust the source.
You will likely see a message telling you to switch on the toolbar button. That is expected; the platform is telling you algorithmic trading has not been enabled yet (MetaTrader help). I left it until the second robot was attached, then enabled it once.
Step 7: Set the Platform to Restart Automatically
Servers reboot. Sometimes for updates, sometimes for provider maintenance, occasionally for reasons nobody explains. If your platform does not relaunch afterward, your robots are offline and you may not notice for hours.
Dipgate users: place a shortcut to the platform in the preconfigured My Platforms Autostart folder on the desktop.
Here is what I did:
- Open Windows File Explorer on the VPS
- Go to the C drive, then Program Files
- Find your platform folder, in my case BlackBull Markets MetaTrader 5
- Right-click the terminal executable, terminal64.exe on 64-bit installs or terminal.exe on 32-bit, and copy it
- Open My Platforms Autostart, right-click, and choose Paste Shortcut
Paste a shortcut, not the executable itself. Copying the actual program file out of its installation directory breaks it.
A notification confirmed the terminal was now configured to run at login. That confirmation is what you want to see, though it is not proof the recovery works, which is what Step 8 exists for.
If Your Provider Has No Autostart Folder
| Environment | Method |
| Dipgate server with the provided folder | Use My Platforms Autostart |
| Standard Windows VPS | Press Windows and R, type shell:startup, and place the shortcut there |
| Setups needing higher reliability | Create a Task Scheduler task triggered at startup or logon, with restart-on-failure enabled |
| Managed trading VPS | Follow the provider’s documented startup service |
Task Scheduler is the more dependable option of the three, because it can relaunch the platform if the process dies rather than only at login. Slightly more work. Worth it on accounts that matter.
Step 8: Test the Whole Setup, Then Reboot
A terminal that looks fine right now is not a terminal proven to recover. Work through this before walking away.
- Confirm MetaTrader shows an active broker connection
- Check the account number and server displayed are the ones you intended
- Confirm each robot is attached to the correct symbol and timeframe
- Confirm algorithmic trading is enabled globally and within each EA’s settings
- Review the Experts and Journal tabs for errors
- Save your EA inputs as a preset file so a reinstall does not mean reconfiguring from memory
- Restart the VPS
- Confirm the platform launches by itself
- Confirm the account reconnects and every robot reloads
- Verify no duplicate copy of the same EA is running on another machine or server
- Set up an external uptime or account alert so you learn about failures from a notification rather than from your equity curve
Point 10 deserves emphasis. Running the same robot on the same account from two terminals produces duplicate orders, and traders discover this at the worst possible moment.
Disconnect. Do Not Sign Out.
When you finish working, close the Remote Desktop window to disconnect the session.
Do not select Sign Out from the Windows menu, do not shut the server down, and do not close MetaTrader. Depending on configuration, signing out can terminate running applications, which stops your robots without any obvious warning.
Check with your provider whether their setup keeps applications running after disconnection. Most trading-focused hosts configure this correctly; assuming it rather than confirming it is how people lose a week of trading.
Completion Checklist
| Check | Required result |
| Remote Desktop security | IP verified, temporary password changed |
| Windows updates | Pending security patches installed |
| Broker connection | Correct account and server connected |
| EA location | Correct MQL4 or MQL5 Experts folder |
| Permissions | Algorithmic trading enabled, DLL access granted only where needed |
| Symbol and timeframe | Match the EA documentation |
| Logs | No unresolved Experts or Journal errors |
| Startup | Platform relaunches after a reboot, verified not assumed |
| Session handling | Disconnected rather than signed out |
| Duplicate protection | Each robot runs from one terminal only |
| Monitoring | External alert or account tracker active |
| Backup | Presets, templates, and license details stored securely |
Work through that list and your platform is trading from the cloud. Electricity, internet outages, and an accidentally closed laptop stop being your problem, which was the entire reason for doing any of this.
The Latency Reading, and What It Does Not Prove
After finishing, MetaTrader displayed a lowest connection reading of 1.33 milliseconds between this Dipgate server and the BlackBull Markets endpoint I was connected to.
Some honesty about that figure:
- It was a single observation during one setup session, not a controlled execution test
- It reflects the platform’s displayed connection reading rather than a benchmarked network measurement across many samples
- Network latency says nothing about slippage, fill quality, liquidity, or spread
- Your own reading depends on which data center you choose and which broker endpoint you connect to
[Note for publication: add the Dipgate data center location, the BlackBull server name, the date and time of the reading, and lowest, median and average results if you captured them.]
What I can say with more confidence is directional. A VPS hosted near your broker’s servers will generally produce a lower reading than a home connection routed across a continent, sometimes dramatically so. Measure both rather than trusting a general range, since home latency varies enormously by provider, route, and geography.
Whether the difference matters depends on your strategy. A swing system holding positions for days will not notice. Scalping, high-frequency logic, and news-adjacent systems will.
The practical instruction stays simple: pick a server location close to your broker. Dipgate publishes a broker latency tool for exactly this, with data centers in financial hubs including London, New York, Amsterdam, Singapore, Zurich, and Tokyo (provider site). If unsure which location suits your broker, use the tool or ask your broker directly.
We use Dipgate at Algo Trading Space for the low latency and the range of trading servers available. Our own VPS comparison rates them well for scalping and high-frequency forex EA trading, though other providers win on different criteria.
What Goes Wrong, and Why
| Symptom | Likely cause |
| Remote Desktop rejects the password repeatedly | Local username appended instead of Administrator |
| Platform offline after a reboot | Autostart never configured, or configured but never tested |
| Robots stopped after you closed the session | Signed out of Windows instead of disconnecting |
| EA sits in the folder but not in Navigator | Refresh not performed, or an uncompiled source file |
| Nothing trades despite everything looking correct | Algorithmic trading disabled, or permissions declined at attachment |
| Terminal slows during volatile sessions | Too many charts, symbols, or background applications |
| Latency worse than expected | Server location chosen without reference to broker hosting |
| Duplicate orders appearing | Same EA running from a second terminal |
None of these are complicated. All of them cost money at the wrong moment.
Choosing a Provider: What I Would Check
| Criterion | Why it matters | What to look for |
| Server location | Determines real latency | A data center near your broker |
| Latency tool | Removes guesswork | Published broker figures you can check before buying |
| RAM allocation | Governs how many platforms run | Headroom for every terminal plus Windows |
| Storage type | Affects responsiveness | SSD at minimum, NVMe storage where offered |
| Dedicated resources | Stops other tenants slowing you | Clear allocation rather than shared pooling |
| Startup handling | Keeps you trading after reboots | A documented folder, service, or scheduled task |
| Session persistence | Applications survive disconnection | Explicit confirmation, not assumption |
| Security controls | Protects credentials | Firewall, allowlisting, multifactor options |
| Support hours | Markets run around the clock | Round-the-clock contact |
| Trial or refund window | Lets you measure first | Something better than a hard annual commitment |
One opinion, freely offered: traders overweight raw specifications and underweight location. A modest server next to your broker beats a powerful one on the wrong continent for anything latency-sensitive. Exceptions exist, particularly when running many platforms at once, and at that point a dedicated server becomes worth comparing.
Should You Even Use a VPS?
Hosting earns its cost if:
- You run robots that need to trade while you sleep
- Your home connection or power supply is unreliable
- Execution timing genuinely affects your strategy
- You run several platforms and would rather not tie up your own machine
You can probably skip it if:
- You trade manually during set hours and close everything afterward
- You already have a machine that stays powered on with stable connectivity
- Your strategy holds positions for days and cares nothing about milliseconds
The honest position: hosting solves a reliability problem, not a profitability one. It will not fix a losing system. What it removes is the category of loss that has nothing to do with your strategy, namely the power cut, the router restart, and the Windows update at three in the morning.
Frequently Asked Questions
Can I connect to a trading VPS from a Mac or phone?
Yes, though the tooling has changed. Microsoft has been replacing the older Remote Desktop clients with Windows App on macOS, iOS and iPadOS, and Android or ChromeOS, and its documentation now points users toward that application. Check current Microsoft guidance before downloading, since availability by platform shifts. Practically, initial setup is far easier on a desktop where copying files between machines is straightforward; mobile access suits checking positions or restarting a platform rather than performing installations.
How much RAM do I need for multiple MetaTrader platforms?
Each terminal typically consumes several hundred megabytes once charts and indicators load, so requirements scale with how many platforms and charts you run rather than with account size. Windows itself needs allocation before any trading software opens. Traders running one or two terminals manage on entry-level plans; anyone hosting five or more should size upward. Reducing open charts and hiding unused symbols lowers consumption meaningfully, which is why the housekeeping steps in this guide matter.
Will my broker give me a free VPS instead?
Many brokers offer hosting once monthly volume passes a threshold, which suits consistently active traders. Terms vary considerably between firms, so check whether the service permits other brokers, grants administrator access, allows custom software, and continues if your volume falls below the eligibility level. Independent providers cost money and give you freedom over data center choice and configuration regardless of activity. Read the specific offer rather than assuming a general pattern applies.
What happens to my open trades if the VPS goes offline?
Positions already opened remain live at your broker, since orders sit on broker servers rather than your terminal. What stops is management: trailing stops handled by the robot, pending grid entries, and any exit logic requiring the platform to be running. Stop loss and take profit levels already submitted to the broker stay active. This distinction is precisely why startup configuration, reboot testing, and external monitoring deserve attention before problems occur rather than after.
Do I need a separate license to run my EA on a VPS?
That depends on the vendor. Some robots bind licenses to an account number, meaning the same license works wherever the platform runs. Others bind to hardware identifiers and require reactivation after moving to a server. Check licensing terms before installing and contact the developer if uncertain, since discovering a restriction after funding creates avoidable friction. Free expert advisors frequently include multiple flexible licenses that cover this situation without additional steps.
Can I install indicators and custom tools the same way?
Yes, with one folder difference. Indicators go into the Indicators folder inside the data directory rather than Experts, and scripts belong in Scripts. Reach all of them through File, then Open Data Folder, then the MQL4 or MQL5 folder. Refresh the Navigator panel afterward exactly as you would for a robot. Compiled files carry .ex4 or .ex5 extensions; source files need compiling in MetaEditor before the platform recognizes them.
How do I move an existing setup to a new server?
Copy your robot and indicator files, note every account number and server name, and export chart templates and preset files before starting. Install the platform fresh on the new machine rather than copying the whole program folder, since installations register components with Windows. Reattach robots, reapply settings, configure startup, and run the reboot test. Disable the old setup before enabling the new one to avoid duplicate orders reaching your broker from two terminals.
You can compare the hosting providers we actually use, including the one featured here, on our VPS providers page.
Our VIP Club members get live trading results, early insight before articles go public, and priority support when a setup question needs answering quickly. If you would rather have the whole configuration built for you, our premium setup covers portfolio construction, broker account preparation, hosting, and platform configuration.
Disclosure: Algo Trading Space may earn a commission from some links on this page. It does not affect which providers we use ourselves or what we publish about them.
Risk warning: Trading leveraged products carries a high risk of losing money rapidly. Hosting improves reliability and connection conditions; it does not make a strategy profitable. The latency reading quoted here came from one connection between one provider and one broker at a single moment, and it does not measure execution quality. Trade only with capital you can afford to lose. Nothing here constitutes investment advice.
