MetaTrader VPS Setup: Run MT4/MT5 EAs 24/7 on Windows

In short

A MetaTrader VPS is a remote Windows environment that keeps MT4 or MT5 running even when your own computer is off. The practical setup is: deploy a Windows VPS, connect over RDP, install the broker's MetaTrader terminal, copy your EAs and profiles, verify the broker server, enable automated trading, then disconnect from RDP without signing out so the Windows session stays active.

For one light terminal, 2 vCPU and 4 GB RAM is usually a sensible starting point. Multiple terminals, heavy indicators, or strategy testing need more headroom. If your EA depends on DLLs, multiple terminals, custom scripts, or Windows-level tools, a full Windows VPS is more flexible than MetaTrader's built-in Virtual Hosting.

MetaTrader VPS vs MetaTrader Virtual Hosting

MetaTrader users can choose between two different hosting models:

MetaTrader's own Virtual Hosting is integrated into the platform and is designed around migration from the local terminal. It is not a general-purpose Windows desktop.

One important limitation: MetaQuotes documentation states that DLL calls are not allowed in the virtual hosting environment. If your EA requires trusted DLLs or other Windows-level dependencies, use a full Windows VPS instead.

A useful decision rule is:

Need only MetaTrader-native EA/signal hosting
→ MetaTrader Virtual Hosting can be simpler

Need full Windows control, RDP, multiple terminals,
custom tooling, DLLs, or file automation
→ Windows VPS

Why run MT4 or MT5 on a Windows VPS?

A Windows VPS gives MetaTrader a remote desktop that can remain online independently of your laptop.

That helps when you need:

• 24/7 EA availability;
• MT4 or MT5 running while your own PC is off;
• several terminals or broker accounts;
• remote administration over RDP;
• a consistent Windows environment;
• central files, presets, templates, and logs;
• controlled Windows updates and reboot windows;
• access from another computer or mobile RDP client.

A VPS does not guarantee trading profits, broker execution, low slippage, or a particular latency result. It only provides the infrastructure layer.

Step 1 — Choose the VPS around the MetaTrader workload

MetaTrader itself is usually light, but the complete workload can grow quickly as you add terminals, charts, EAs, historical data, and backtesting.

These are planning ranges, not guarantees. EA code quality, indicator load, tick frequency, chart count, and tester jobs can change CPU use dramatically.

For MetaTrader, it is usually better to leave headroom than to run the VM near 100% CPU or RAM during live automation.

Step 2 — Connect to the Windows VPS over RDP

After the VM is running, connect with Remote Desktop.

Use:

Computer: VPS public IP
Username: Administrator
Password: your Windows VPS password

For the full first-login workflow, use How to Connect to a Windows VPS via RDP.

After first login:

1. Run Windows Update.
2. Reboot if required.
3. Reconnect.
4. Confirm the server time and time zone.
5. Confirm internet access.
6. Save credentials in a password manager.

Do not install trading software before the Windows Server is patched and stable.

Step 3 — Install MT4 or MT5 from the broker or MetaQuotes

Prefer the installer from your broker's official client portal when you are connecting a live account. Broker-provided packages often include the correct server list and connection settings.

Use an official MetaQuotes download only when appropriate for your account.

Avoid random third-party installers.

After installation:

1. Open MetaTrader.
2. Log in to the trading account.
3. Select the exact broker server.
4. Confirm the connection indicator.
5. Check the Journal tab for login errors.
6. Verify the account number and server before enabling automation.

If the account connects on your home PC but not on the VPS, the first thing to compare is the broker server name, not the VPS itself.

Step 4 — Move an existing MT4/MT5 setup without breaking profiles or EAs

If you already have MetaTrader configured on another computer, migrate the application data rather than rebuilding every chart manually.

On the source MetaTrader terminal:

File
→ Open Data Folder

Important folders include:

Safe migration sequence:

1. Close MetaTrader on both source and VPS.
2. Back up the source data folder.
3. Copy only the folders you actually need.
4. Start MetaTrader on the VPS.
5. Open the correct charts and profiles.
6. Verify every EA and indicator loads.
7. Re-enter vendor license details if the EA binds to a new machine.
8. Confirm symbols, timeframes, and broker suffixes match.

Do not assume a copied profile proves the EA is operational. Check the Experts and Journal tabs after migration.

Step 5 — Install and verify Expert Advisors

For MT4:

MQL4
→ Experts

For MT5:

MQL5
→ Experts

After copying the EA:

1. Restart MetaTrader or refresh Navigator.
2. Open the required chart.
3. Attach the EA.
4. Load the correct preset if you use a .set file.
5. Confirm automated trading permission.
6. Check whether DLL or WebRequest access is required.
7. Read Experts and Journal for errors.

Only enable DLL imports for software you trust. DLLs execute native code inside Windows and should be treated like any other executable dependency.

Step 6 — Keep MetaTrader running after Remote Desktop disconnects

This is the most important operational step.

When you finish managing the VPS, disconnect from RDP. Do not sign out of Windows.

Correct:

Close the RDP window
or
Disconnect the RDP session

Avoid:

Start → Sign out

or:

logoff

Signing out ends the Windows desktop session and normally closes GUI applications running in that session, including MetaTrader.

After disconnecting, reconnect later and verify:

• MetaTrader is still open;
• account connection is active;
• the EA is still attached;
• Algo Trading / AutoTrading is enabled;
• no repeated Journal or Experts errors appeared.

Step 7 — Start MetaTrader again after planned reboots

An RDP disconnect keeps the current user session alive, but a Windows reboot ends it.

For a simple environment, place a MetaTrader shortcut in the Startup folder:

Win + R
shell:startup

A more controlled option is Task Scheduler:

Trigger: When I log on
Action: Start terminal.exe or terminal64.exe

Do not treat MetaTrader as a Windows service unless the software vendor explicitly supports that architecture. It is a desktop application.

After every reboot:

1. Sign in.
2. Confirm MetaTrader launches.
3. Confirm broker connection.
4. Confirm EA state.
5. Check logs.

Step 8 — Monitor MT5 or MT4 from a phone

A VPS does not require you to keep an RDP session open all day.

For account monitoring, the cleaner approach is usually:

• use the broker's official MT4/MT5 mobile app for positions and account status;
• use RDP from a phone only when you need to administer the Windows terminal itself;
• configure EA/vendor notifications where supported;
• review Journal and Experts logs during scheduled checks.

This reduces the temptation to leave a Remote Desktop session open continuously.

Step 9 — Troubleshoot “No connection” on a MetaTrader VPS

Do not assume every MetaTrader connectivity problem is a VPS outage.

Check in this order:

1. VPS internet access

Open a browser on the VPS and confirm normal internet connectivity.

2. Broker server selection

Confirm the exact server name used by the account.

3. Account type

Check whether the login is MT4 or MT5 and whether it is demo or live.

4. MetaTrader Journal

Look for:

• authorization failed;
• no connection;
• invalid account;
• server unavailable;
• network or proxy errors.

5. Broker status

If other applications on the VPS work but MetaTrader cannot reach the broker, verify the broker's server status before changing Windows Firewall.

The useful diagnostic split is:

No internet on VPS
→ infrastructure/network issue

Internet works, broker server unreachable
→ broker/routing/terminal issue

Broker connects, EA still fails
→ EA/configuration/permission issue

Step 10 — Troubleshoot an EA that works on your PC but not on the VPS

Common causes include:

• Algo Trading disabled;
• EA-level trading permission disabled;
• wrong chart or timeframe;
• different symbol name or suffix;
• missing indicator dependency;
• missing DLL;
• DLL permission disabled;
• missing WebRequest domain;
• vendor licence tied to the old machine;
• missing .set preset;
• Windows path differences;
• broker account or server mismatch.

Check:

Tools
→ Options
→ Expert Advisors

Then inspect Experts and Journal. If the EA is loaded but never sends a trade request, do not immediately resize the VPS. First rule out strategy conditions and permissions.

Step 11 — Separate RDP performance from trading-platform connectivity

A slow Remote Desktop session does not automatically mean MetaTrader is disconnected from the broker.

RDP responsiveness depends on your client-to-VPS path. MetaTrader broker connectivity depends on the VPS-to-broker path.

If RDP feels slow but MetaTrader shows a stable broker connection and normal logs, the trading terminal may still be operating correctly.

For RDP troubleshooting, see Remote Desktop Slow? Improve RDP Performance.

Step 12 — Back up the MetaTrader environment

Back up the MetaTrader data folder before:

• changing EA versions;
• changing parameters;
• moving to another VPS;
• upgrading MetaTrader;
• changing broker account;
• cleaning profiles or templates;
• making large Windows changes.

Keep copies of:

• MQL4 or MQL5;
• profiles;
• templates;
• presets;
• vendor configuration files;
• relevant logs;
• screenshots or reports you rely on.

Store an off-server copy. A backup stored only on the same VM does not protect against VM loss or accidental deletion.

Step 13 — Secure the trading VPS

Treat the VPS as a system containing financial-account credentials and executable trading code.

Use:

• strong unique Windows credentials;
• Windows Firewall;
• Windows Update;
• trusted EA sources only;
• no cracked EAs or indicators;
• no public SMB shares;
• restricted RDP access where practical;
• backups and restore checks;
• separate passwords for broker and VPS;
• a password manager.

If you can restrict RDP by trusted source IP or use a controlled access path, do so.

Choosing latency for MetaTrader

Latency should be measured against the broker's actual trade server, not against your own physical location.

The number that matters is the VPS-to-broker path.

Execution also depends on:

• broker infrastructure;
• liquidity routing;
• account type;
• spread;
• slippage;
• order type;
• market volatility;
• EA logic.

A hosting provider cannot guarantee broker execution quality or trading results.

How Raff fits MetaTrader VPS workloads

Raff provides Windows VM infrastructure where traders can install MT4 or MT5, connect over RDP, run multiple terminals, manage files, and operate trusted EAs or indicators.

Raff's role is the infrastructure layer, not the brokerage or trading-strategy layer.

Raff does not provide:

• broker services;
• trading advice;
• profitability guarantees;
• EA certification;
• account management;
• broker execution guarantees.

For a customer-managed setup, use the current Raff Windows VM plans and size the VM around the number of terminals, EAs, charts, and tester workload.

If your main intent is specifically forex trading infrastructure, compare that with Raff's dedicated Forex VM product page rather than using this tutorial as the pricing page.

Compatible with Raff

This article documents a customer-managed MetaTrader architecture that is compatible with Raff Windows VMs. The current article does not make a fresh “Tested on Raff” claim because it does not include a complete new test environment, dated engineer validation, and original MetaTrader screenshot set required by Raff's Windows editorial standard.

What's next

• Windows application hosting — review the broader Windows application-hosting model when comparing persistent business workloads.
• How to Connect to a Windows VPS via RDP
• Remote Desktop Slow? Improve RDP Performance
• Windows Server 2019 vs 2022 vs 2025
• Configure Windows Firewall on a Windows VPS
• Raff Windows VM
• Raff Forex VM

Sources

• MetaTrader 5 Help — Virtual Hosting
• MetaTrader 5 Help — Migration to Virtual Hosting
• MetaTrader 5 Help — Expert Advisors and Custom Indicators
• MetaTrader 5 Help — Strategy Tester
• Microsoft Learn — Remote Desktop Services overview
• Sources verified: 2026-09-09

MetaTrader, MetaTrader 4, MetaTrader 5, MQL4, MQL5, and MetaQuotes are trademarks or products of MetaQuotes Ltd. Raff is not affiliated with or endorsed by MetaQuotes or any broker. This article is technical infrastructure documentation and is not financial advice.