MetaTrader VPS Setup for 24/7 EA Trading (Windows)

A MetaTrader VPS setup means running MetaTrader 4 or MetaTrader 5 on a remote Windows Server so the trading terminal, Expert Advisors, indicators, and signal tools can stay online even when your personal computer is turned off.

The clean setup is:

Deploy Windows VPS
Connect over RDP
Install MT4 or MT5 from your broker or MetaQuotes
Log in to your trading account
Install Expert Advisors / indicators
Enable automated trading only after testing
Configure startup behavior
Keep the RDP session disconnected, not signed out
Monitor Journal and Experts logs
Back up the MetaTrader data folder

The most important operational rule:

Disconnect from RDP. Do not sign out.

If you sign out of Windows, MetaTrader usually closes because it is a desktop application running inside that user session.

A Windows VPS is useful for MetaTrader because it gives you a remote Windows environment with persistent internet access, full administrator control, and RDP access. It does not guarantee profits, execution quality, broker acceptance, or a specific latency result.

Important trading risk note

This article is technical infrastructure documentation.

It does not provide trading advice, financial advice, investment recommendations, broker recommendations, or strategy recommendations.

A VPS can help keep MetaTrader online. It cannot make an Expert Advisor profitable, remove market risk, prevent slippage, guarantee order execution, or protect against broker-side outages.

Before running any Expert Advisor or signal subscription on a live account:

• test it on a demo account;
• understand the strategy;
• review logs;
• confirm lot sizing;
• check max drawdown behavior;
• verify broker rules;
• understand spread and slippage risk;
• keep your own backups;
• accept that automated trading can lose money.

Infrastructure improves availability. It does not remove trading risk.

Quick verdict

Simple rule:

MetaTrader built-in VPS = simple EA/signal migration.
Windows VPS = full control over the Windows trading environment.

MetaTrader built-in VPS vs Windows VPS

MetaTrader 5 includes built-in Virtual Hosting, which is designed to run trading robots and signal subscriptions 24/7, close to broker infrastructure, with migration from inside the trading platform.

That is different from renting a full Windows VPS.

MetaTrader built-in VPS

MetaTrader Virtual Hosting is useful when you want:

• EA or signal subscription migration from inside MetaTrader;
• minimal server management;
• a setup that is tightly integrated with the MetaTrader platform;
• no Windows desktop administration;
• simple 24/7 operation for one MetaTrader environment.

Trade-off:

• less Windows-level control;
• not designed for general server use;
• less flexibility for custom tools;
• not ideal if you need several terminals, custom file workflows, or full Windows administration.

Windows VPS

A Windows VPS is useful when you want:

• full Windows desktop access;
• RDP control;
• multiple MT4/MT5 terminals;
• custom indicators and EAs;
• broker-specific installers;
• scripts and file automation;
• custom backup process;
• control over Windows updates and startup behavior;
• ability to run other supporting tools.

Trade-off:

• you manage Windows;
• you manage security;
• you manage backups;
• you must keep MetaTrader running correctly;
• latency depends on VPS location, broker server location, routing, and broker execution.

For many traders, the Windows VPS model is easier to understand because it behaves like a remote Windows computer.

MT4 vs MT5 on a VPS

Both MetaTrader 4 and MetaTrader 5 are commonly used on Windows VPS environments.

Use the platform your broker supports and your EA requires.

Do not assume an MT4 EA works on MT5.

Do not assume an MT5 EA works on MT4.

The scripting languages, platform behavior, broker symbols, account types, and execution details can differ.

Choosing VPS location

Latency matters for some automated strategies, but it is often misunderstood.

A VPS close to your broker's trading server can reduce network delay between the terminal and broker.

But execution quality also depends on:

• broker server location;
• broker routing;
• liquidity provider;
• account type;
• spread;
• slippage;
• market volatility;
• EA logic;
• order type;
• trade size;
• broker execution model.

Choose a VPS region based on the broker server you actually use, not your home location.

If your broker has servers in New York or nearby US infrastructure, a US-based VPS can make sense.

If your broker server is in London, Frankfurt, Singapore, or Tokyo, test latency carefully before committing.

Inside MetaTrader, check the connection status and ping to the broker server.

Document the number, but do not treat it as a permanent guarantee.

Routing can change.

VPS sizing for MetaTrader

MetaTrader itself is not usually heavy, but multiple terminals, charts, indicators, logs, and strategy testing can use meaningful resources.

Practical sizing:

Storage needs are usually modest, but leave room for:

• platform files;
• logs;
• historical data;
• tester cache;
• screenshots;
• EA files;
• backups.

If you run many terminals, logs and history data can grow over time.

What you will build

Target setup:

Your laptop
  ↓ RDP
Raff Windows VPS
  ├── MetaTrader 4 or MetaTrader 5
  ├── Broker login
  ├── Expert Advisors / indicators
  ├── AutoTrading enabled after testing
  ├── Startup shortcut or scheduled launch
  ├── Journal and Experts logs
  └── Backups of the MetaTrader data folder

The VPS stays online even when your laptop is off.

You connect only when you need to check, update, or manage the terminal.

What you'll need

Prepare:

• Raff Windows VPS or similar Windows Server VPS;
• RDP access;
• broker-supported MT4 or MT5 installer;
• broker account login details;
• read-only investor password if someone only needs monitoring access;
• Expert Advisor files if used;
• indicator files if used;
• license keys for purchased EAs if required;
• basic backup plan;
• 30-60 minutes for first setup.

Do not store broker passwords in plaintext files.

Use a password manager.

Step 1 — Deploy a Windows VPS

Deploy a Windows VPS with enough CPU and RAM for the number of terminals you plan to run.

For most users:

2 vCPU / 4 GB RAM

is a reasonable starting point for one terminal.

Use more headroom if:

• multiple terminals run at once;
• several EAs run at once;
• the account uses many charts;
• historical data downloads are large;
• the VPS also runs monitoring tools;
• you backtest or optimize on the VPS.

Choose Windows Server 2022 or Windows Server 2025 based on your broker's MetaTrader installer compatibility.

MetaTrader is a Windows desktop application, so both usually work, but test the broker-specific installer before production use.

Step 2 — Connect over RDP

Open Remote Desktop from your local machine and connect to the VPS.

Use:

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

After login:

1. Run Windows Update.
2. Reboot if required.
3. Reconnect.
4. Confirm time zone.
5. Confirm internet access.
6. Confirm browser download works.

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

Step 3 — Download MetaTrader

Download MetaTrader from one of these sources:

• your broker's client portal;
• your broker's official MT4/MT5 download page;
• the official MetaTrader 5 download page;
• MetaQuotes or MQL5 resources where appropriate.

Prefer the broker-provided installer when using a live broker account.

Why?

Because broker installers often include the correct server list, branding, and connection configuration.

Avoid random third-party MetaTrader downloads.

They can include outdated builds, wrong broker configuration, or unwanted software.

Step 4 — Install MetaTrader

Run the MT4 or MT5 installer as Administrator.

Use the default install path unless you have a reason to change it.

After installation:

1. Open MetaTrader.
2. Log in to your broker account.
3. Select the correct broker server.
4. Confirm the connection status.
5. Open the relevant symbols in Market Watch.
6. Check the Journal tab for login or connection errors.

If login fails, confirm:

• account number;
• password;
• server name;
• account type;
• broker restrictions;
• MFA or security requirements;
• whether the account is MT4 or MT5.

MT4 credentials do not necessarily work in MT5, and MT5 credentials do not necessarily work in MT4.

Step 5 — Open the MetaTrader data folder

MetaTrader keeps EAs, indicators, profiles, logs, templates, and configuration in the data folder.

In MetaTrader:

File
  → Open Data Folder

Important folders:

This folder is the one you should back up before major changes.

Step 6 — Install Expert Advisors or indicators

For MT4:

MQL4
  → Experts

For MT5:

MQL5
  → Experts

Copy your .ex4, .mq4, .ex5, or .mq5 files into the correct folder.

Then restart MetaTrader or refresh the Navigator panel.

To attach an EA:

1. Open the chart and timeframe required by the strategy.
2. Drag the EA from Navigator to the chart.
3. Confirm EA inputs.
4. Check the EA smiley/icon/status.
5. Enable automated trading only when you are ready.
6. Watch the Experts and Journal tabs.

Only run one EA per chart unless the strategy is specifically designed otherwise.

Step 7 — Enable automated trading safely

In MetaTrader, automated trading usually requires two things:

1. Global automated trading enabled in platform options.
2. EA-level permission enabled on the chart.

For MT5:

Tools
  → Options
  → Expert Advisors

Review:

• Allow algorithmic trading;
• allow DLL imports only if the EA requires it and you trust it;
• allow WebRequest only for trusted URLs if required.

For MT4:

Tools
  → Options
  → Expert Advisors

Then check the AutoTrading or Algo Trading button on the toolbar.

Do not enable DLL imports for unknown EAs.

Do not enable WebRequest to unknown domains.

Purchased or downloaded EAs can execute trading logic and sometimes interact with external services.

Treat them like production software.

Step 8 — Test on demo before live

Before running a live EA:

1. Use a demo account.
2. Confirm the EA loads without errors.
3. Confirm symbols match your broker naming.
4. Confirm lot size.
5. Confirm spread behavior.
6. Confirm stop-loss and take-profit rules.
7. Confirm max trades.
8. Confirm trading hours.
9. Confirm news filters if used.
10. Review the Experts tab.

If the EA has a Strategy Tester path, test it there first.

MetaTrader 5 Strategy Tester supports testing and optimization of Expert Advisors using historical data and can run many optimization passes with different parameters.

Backtesting does not guarantee future performance, but it can catch configuration mistakes before live trading.

Step 9 — Keep MetaTrader running after RDP disconnect

This is the most common VPS mistake.

When you are finished checking MetaTrader, close the RDP window or disconnect.

Do not click:

Start → Sign out

Do not run:

logoff

If you sign out, the desktop session closes and MetaTrader closes.

Correct behavior:

Disconnect RDP session

MetaTrader should continue running in the disconnected user session.

You can also lock the session:

Win + L

Then disconnect.

After reconnecting later, confirm:

• terminal is still open;
• connection is active;
• EA is still attached;
• AutoTrading/Algo Trading is still enabled;
• Journal logs are normal.

Step 10 — Start MetaTrader automatically after login

For simple setups, add MetaTrader to the Startup folder.

Press:

Win + R
shell:startup

Create a shortcut to MetaTrader there.

This starts MetaTrader when that Windows user logs in.

A more controlled method is Task Scheduler:

1. Open Task Scheduler.
2. Create Basic Task.
3. Trigger: When I log on.
4. Action: Start a program.
5. Program: path to terminal.exe or terminal64.exe.

Important:

MetaTrader is a GUI desktop application. Starting it at system boot without an interactive user session can be unreliable.

A scheduled task at user logon is safer than pretending MetaTrader is a Windows service.

For serious unattended setups, plan maintenance windows and reboot recovery manually.

Step 11 — Control Windows updates

Windows updates are important, but random reboots can interrupt MetaTrader.

Use a planned update process:

• choose a maintenance window outside your trading strategy's active hours;
• check open positions before reboot;
• stop EAs if required;
• install updates;
• reboot;
• reconnect;
• verify MetaTrader starts;
• verify account connection;
• verify EAs are active;
• check Journal and Experts logs.

Do not disable updates forever.

A trading VPS exposed to the internet still needs security patches.

The goal is controlled updates, not no updates.

Step 12 — Back up MetaTrader configuration

Back up the data folder before:

• changing EA versions;
• changing input parameters;
• changing broker account;
• moving to another VPS;
• installing many indicators;
• cleaning logs;
• updating platform builds;
• changing templates or profiles.

In MetaTrader:

File → Open Data Folder

Back up:

• MQL4 or MQL5;
• Profiles;
• Templates;
• Presets;
• key log folders;
• screenshots or reports if used.

Do not rely only on screenshots of settings.

Save .set files for EA inputs.

Store backups off the VPS if the trading setup matters.

Step 13 — Monitor logs

Check these tabs inside MetaTrader:

Common messages to investigate:

• invalid stops;
• trade disabled;
• market closed;
• not enough money;
• invalid volume;
• off quotes;
• requote;
• no connection;
• authorization failed;
• DLL imports disabled;
• WebRequest not allowed.

Do not ignore repeated errors.

An EA can be "running" but failing every trade request.

Step 14 — Secure the VPS

A MetaTrader VPS often contains broker credentials and trading software.

Secure it.

Minimum checklist:

• strong Administrator password;
• no shared admin account for a team;
• RDP restricted by IP if possible;
• Windows Firewall enabled;
• Windows Update enabled;
• only trusted EA files installed;
• no random cracked EAs or indicators;
• broker password stored in a password manager;
• investor password used for read-only access;
• backups protected;
• clipboard and drive redirection limited if needed;
• no public file shares;
• no unnecessary ports exposed.

If you use purchased EAs, keep license keys secure.

Do not upload broker passwords, .set files, logs, or screenshots publicly without review.

Common errors and fixes

Error 1 — MetaTrader closes when I disconnect

You probably signed out instead of disconnecting.

Fix:

• log back in;
• open MetaTrader;
• check EA and account status;
• disconnect by closing the RDP window instead of signing out.

Error 2 — EA is attached but not trading

Check:

• AutoTrading/Algo Trading button;
• EA settings;
• symbol name;
• chart timeframe;
• lot size;
• broker trading permissions;
• account type;
• market hours;
• minimum stop level;
• margin;
• Experts tab errors;
• Journal tab errors.

Do not assume it is a VPS problem.

Most EA failures are configuration, broker, or strategy rules.

Error 3 — "No connection" or login failed

Check:

• broker server selected correctly;
• account number;
• password;
• broker server status;
• VPS internet access;
• firewall or proxy;
• broker account restrictions;
• MT4 vs MT5 mismatch.

If the broker changed server names, reinstall the broker-provided terminal or rescan servers.

Error 4 — EA needs WebRequest

Some EAs call external URLs.

Enable only trusted URLs:

Tools
  → Options
  → Expert Advisors
  → Allow WebRequest for listed URL

Add only the exact domains required by the EA vendor.

Do not allow unknown URLs.

Error 5 — DLL imports disabled

Some EAs require DLL imports.

Only enable DLL imports if:

• you trust the EA vendor;
• the DLL is from a known source;
• you understand the security risk;
• the EA documentation requires it.

DLLs are executable code.

Treat them carefully.

Error 6 — VPS rebooted and MetaTrader did not restart

MetaTrader usually starts when a user logs in, not before.

Fix:

• add MetaTrader to Startup folder;
• create a Task Scheduler trigger at user logon;
• after planned reboot, log in and confirm;
• avoid unscheduled reboots during trading hours.

Do not assume a GUI trading terminal behaves like a background service.

Error 7 — High CPU usage

Possible causes:

• too many charts;
• too many indicators;
• too many terminals;
• aggressive tick processing;
• strategy testing running;
• EA loop bug;
• logging too much;
• Windows updates;
• antivirus scanning terminal folders.

Fix:

• reduce charts;
• close unused symbols;
• reduce indicators;
• split terminals across larger VM;
• review EA behavior;
• avoid running Strategy Tester during live trading.

Error 8 — RDP is slow but MetaTrader still works

RDP performance and broker execution are not the same.

If the desktop feels slow:

• reduce RDP resolution;
• reduce color depth;
• disable visual effects;
• close extra apps;
• check CPU/RAM;
• use a closer RDP client network;
• read RDP performance tuning.

If MetaTrader logs show normal broker ping and no connection errors, the trading terminal may still be functioning even if the remote desktop feels sluggish.

Security mistakes to avoid

Avoid:

• running cracked EAs;
• storing broker credentials in plain text;
• exposing RDP to everyone without a strong password;
• disabling Windows Firewall;
• disabling updates forever;
• running unknown scripts as Administrator;
• sharing screenshots with account numbers visible;
• copying terminal folders to third parties without cleaning logs;
• testing new EAs on live accounts first;
• using the same password for VPS and broker account.

Treat the VPS as a production financial system.

How Raff fits MetaTrader VPS setups

Raff Windows VPS gives you a Windows Server environment with RDP access and full administrator control.

That fits MetaTrader users who want:

• MT4 or MT5 on a remote Windows desktop;
• 24/7 terminal availability;
• full control over files and indicators;
• multiple terminals or brokers;
• stable Windows infrastructure;
• unmetered bandwidth;
• support for Windows VPS access and infrastructure issues.

Raff does not provide:

• trading advice;
• broker services;
• EA validation;
• profitability guarantees;
• account management;
• financial recommendations;
• MetaQuotes or broker account support.

A practical Raff MetaTrader setup:

Raff Windows VPS
  ↓
RDP access
  ↓
MetaTrader terminal
  ↓
Broker connection
  ↓
EA / indicator / signal tools
  ↓
Monitoring + backups

Use Raff for infrastructure.

Use your broker and MetaTrader vendor resources for trading platform, account, and EA-specific support.

What Raff recommends

For MetaTrader on a Windows VPS:

1. Choose a VPS region based on broker server latency, not your home location.
2. Start with enough RAM headroom.
3. Install MetaTrader from your broker or official source.
4. Test on demo before live.
5. Enable AutoTrading only after reviewing EA settings.
6. Disconnect from RDP instead of signing out.
7. Use Startup folder or Task Scheduler for user-logon startup.
8. Plan Windows updates instead of disabling them forever.
9. Back up the MetaTrader data folder and .set files.
10. Monitor Journal and Experts logs.

The goal is not just to keep a terminal open.

The goal is to run a controlled, monitored, recoverable MetaTrader environment.

Tested on

Compatible with Raff Windows VPS deployments running MetaTrader 4 or MetaTrader 5 over RDP. Do not publish that exact claim until the environment has been tested.

What's next

• Connect to a Windows VPS via RDP
• RDP Performance Tuning for Smooth Remote Desktop
• Windows Server 2019 vs 2022 vs 2025: Which Version to Choose
• Windows Firewall for Production Servers
• Cloud Server Backup Strategies
• Raff Windows VPS

Sources

• MetaTrader 5 — Virtual Hosting for Forex and Stocks Trading
• MetaTrader 5 — Download MetaTrader 5
• MetaTrader 5 Help — Expert Advisors and Custom Indicators
• MetaTrader 5 Help — Strategy Optimization
• Microsoft Learn — Remote Desktop Services overview
• Date last verified: 2026-07-07

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