The one thing to understand first
MetaTrader 4 and 5 are Windows programs. Hostinger VPS plans ship with Linux (typically Ubuntu) and give you full root access, but no Windows template. So every setup on this page is really an answer to one question: how do I get Windows software running on a Linux server? There are three honest answers, and the right one depends on your comfort level — not your budget, because the cheapest path is also the most popular.
Path 1: Wine on Ubuntu (recommended for most)
Wine is a free compatibility layer that translates Windows calls to Linux ones — no Windows license needed, no emulation overhead worth worrying about for an app as light as MT4. This is how the majority of retail traders run MetaTrader on cheap Linux VPS plans, and MT4/MT5 are among Wine’s best-supported applications.
Setup overview
- 1. Spin up the VPS with Ubuntu (22.04 LTS or newer) in the data center closest to your broker — see our forex VPS guide for the location logic. Note the server IP and root credentials.
- 2. Connect over SSH from your computer and update the package lists. If the command line is new to you, this is the steepest five minutes of the whole project — it gets easier from here.
- 3. Install Wine from Ubuntu’s repositories (the stable branch is fine for MT4/MT5). Accept the couple of gigabytes of dependencies without worry.
- 4. Download your broker’s MT4/MT5 installer — use your broker’s branded installer, not the generic MetaQuotes one, so the server list comes pre-configured. Transfer it to the VPS (SCP, SFTP, or a direct download link on the server).
- 5. Run the installer under Wine. It looks exactly like a Windows install wizard because, as far as the installer knows, it is one. Accept the defaults.
- 6. Launch the terminal, log in with your broker account credentials, and confirm you see live prices moving. If prices move, you are done with the hard part.
- 7. Install your EAs/indicators into the Wine-mapped MQL4/MQL5 folders, enable algo trading in the terminal options, and — this is the step everyone skips — restart the terminal once to confirm everything loads cleanly on a fresh start.
The two gotchas to know about
Gotcha 1: graphical quirks. Wine renders MT4/MT5 nearly perfectly, but you may see minor font or chart oddities depending on the Wine version. They are cosmetic — your EAs do not care what the chart looks like. If something looks truly broken, a newer Wine stable release usually fixes it.
Gotcha 2: you are the admin now. There is no control panel babysitting this terminal. Set up basic server hygiene: automatic security updates, a firewall allowing only your SSH and needed ports, and SSH key login instead of passwords. A trading server that gets compromised is worse than no trading server.
Path 2: Windows on the VPS with your own license
Because Hostinger VPS is KVM-virtualized with full root access, you can mount a Windows Server ISO and install it yourself — then MT4/MT5 install natively, exactly like on your home PC, and you manage the box over Remote Desktop. The catch is the license: you must bring a valid Windows Server license, and that cost typically erases the savings versus just buying a dedicated forex VPS with Windows included. This path makes sense mainly if you already own a license or need Windows on the server for other software too.
Path 3: Skip it — dedicated forex VPS
If reading Path 1 made you tired, that is useful information about yourself: buy a dedicated forex VPS where Windows and MT4/MT5 come pre-installed. You will pay more per month and get a less powerful machine, but you will be trading in ten minutes instead of troubleshooting Wine at midnight. There is no shame in this choice — uptime you actually achieve beats uptime you intended. Our best VPS for trading comparison covers the field.
VPS sizing: how much server does MetaTrader need?
Less than you think. A single MT4 terminal is a light application — a few hundred megabytes of RAM at rest, modest CPU while running EAs. Size by terminal count, not by anxiety:
- Entry KVM plan: 1–3 terminals with typical EAs. This is where most retail traders live, permanently.
- One tier up: 4–8 terminals, heavier indicator stacks, or frequent strategy-tester optimization runs — backtesting is the only trading workload that genuinely eats CPU.
- Larger plans: only if you are running a small fleet of terminals or sharing the box with other services (a website, a Discord bot, a data pipeline).
Start small. VPS plans can be scaled up later, and an idle 8-core server does not execute trades any better than an idle 1-core one — it just costs more while doing nothing.
Latency and uptime: setting expectations
Once the terminal is running, two numbers matter. Latency is set by geography: choose the Hostinger data center nearest your broker’s trade server (London broker → UK; New York broker → Phoenix or Boston), and you will land in the low tens of milliseconds — plenty for EAs and scalping at retail scale. Uptime is the real win: your terminal now runs in a data center with redundant power and network, not on a laptop that sleeps when you close the lid. That reliability — not raw speed — is why most traders move to a VPS in the first place.
Frequently asked questions
Not directly — MT4 is a Windows program and Hostinger VPS runs Linux. The standard method is Wine on Ubuntu (free, about an hour of setup), detailed in Path 1 above. Your broker’s branded installer works best since it pre-configures their servers.
About the same. Both run well under Wine. MT5’s 64-bit build is arguably smoother on modern Wine versions, but the practical difference is small — pick the platform your broker and strategy support, not the one that installs 5% easier.
The entry-level KVM plan comfortably runs 1–3 terminals with typical EAs. MetaTrader is light; traders routinely overbuy specs. Scale up only when you add terminals or do heavy backtesting.
Not for the Wine path — that is its main appeal. You only need a Windows license if you choose Path 2 and install Windows on the VPS yourself.
Yes — that is the entire point. The terminal runs on the VPS in the data center, independent of your own computer. Close your laptop, lose your home internet, go on holiday: the EA keeps working.
Wine on a Hostinger VPS is cheaper and gives you a full server for other projects, but you do the setup and maintenance. A dedicated forex VPS costs more monthly but arrives ready with Windows and MT4 pre-installed. Technical traders pick Wine; everyone else should price their own time honestly.
Read the strategy-level view in Hostinger forex VPS, compare providers in best VPS for trading, or grab the VPS plan and start the setup — the 20% first-purchase discount applies in the cart.
Wine troubleshooting: specific errors and fixes
The setup guide covers the happy path. Here are the specific Wine failures traders encounter and their fixes:
| Error / symptom | Likely cause | Fix |
|---|---|---|
| Installer crashes immediately | Missing 32-bit Wine libraries | Install 32-bit Wine alongside 64-bit; MT4's installer needs 32-bit support |
| Terminal launches but shows blank charts | Missing font or rendering libraries | Install corefonts and common graphics libraries in the Wine prefix |
| EA works in strategy tester but not live | Algo trading disabled, or DLL imports blocked | Enable algo trading in terminal options; allow DLL imports for that specific EA |
| Terminal disconnects frequently | Network instability or broker server issues | Check VPS network; try a different broker server from the list; verify firewall allows the broker's ports |
| Wine prefix corruption after update | System update changed Wine version incompatibly | Back up the Wine prefix before system updates; recreate the prefix if corrupted |
The 32-bit library issue deserves emphasis because it is the single most common Wine installation failure. Modern Ubuntu defaults to 64-bit Wine, but MT4's installer is a 32-bit application. The fix is straightforward once you know it, but the error message gives no hint. If the installer fails silently or crashes on launch, install 32-bit Wine support first before debugging anything else.
EA optimization for VPS: settings that actually matter
Running an Expert Advisor on a VPS differs from running it on your home PC in ways that affect performance:
- Disable visual mode in strategy tester. The VPS has no monitor. Visual backtesting wastes CPU rendering charts nobody sees. Run all optimization in non-visual mode.
- Limit chart windows. Each open chart consumes memory and CPU for indicator calculations. On a VPS, keep only the charts your EAs actively trade. Close everything else.
- Reduce max bars in history. In terminal options, limit the bars kept in history and in charts. Excessive history bloats memory usage, especially with multiple EAs on multiple pairs.
- Schedule resource-intensive tasks. Strategy optimization and heavy backtesting should run during off-hours when live trading is quiet. Do not optimize parameters while EAs are executing live trades on the same terminal.
- One terminal per strategy cluster. Rather than running 15 EAs in one terminal, group related EAs (same broker, same timeframe logic) into 2-3 terminals. This isolates crashes: one terminal freezing does not take down all strategies.
Backup and disaster recovery for trading servers
A trading VPS holds more than a website: live positions, EA configurations, custom indicators, and account credentials. Your backup strategy must reflect that.
- What to back up: the entire Wine prefix (contains the terminal installation and all settings), the MQL4/MQL5 folders (EAs, indicators, scripts), terminal configuration files (account logins, chart templates), and any custom scripts or monitoring tools you added.
- Backup frequency: weekly full backups minimum. After any EA parameter change, strategy update, or terminal configuration change, take an immediate backup. The cost of a backup is minutes; the cost of rebuilding from scratch during market hours is real money.
- Off-server storage. Hostinger's VPS snapshots capture the whole disk, which is excellent for disaster recovery. But also keep a copy of critical EA files and configurations somewhere off the VPS (your local machine, cloud storage). If the VPS itself is unreachable, you need the EAs to set up elsewhere.
- Document the setup. Write down (outside the VPS) your broker account numbers, server names, EA parameter sets, and the installation steps. If you need to rebuild from zero at 2am during a market event, documentation is the difference between a 30-minute recovery and a 4-hour panic.
- Test the restore. Annually, restore your backup to a fresh VPS (or the smallest temporary plan) and verify the terminal launches with EAs intact. An untested backup is a theory, not a plan.
Multiple broker accounts on one VPS
Many traders run accounts with 2-3 different brokers. Here is how to structure it:
- Separate Wine prefixes per broker. Install each broker's branded MT4/MT5 in its own Wine prefix. This prevents DLL conflicts, keeps configurations isolated, and lets you update one broker's terminal without affecting others.
- Separate data folders. Each terminal installation maintains its own MQL folders, history, and settings. Do not share EA files across prefixes by symlinking; copy them. Shared files create subtle version conflicts.
- Resource planning. Each additional terminal adds roughly 200-500 MB of RAM depending on charts and EAs. Three brokers with active EAs on an entry KVM plan is comfortable. Five or more terminals with heavy EAs warrants stepping up a plan tier.
- Portable terminals for testing. MT4/MT5 support portable mode (running from a folder without full installation). Use portable installations for testing new EAs or broker connections before committing to a full prefix setup.
The best VPS for trading comparison covers how Hostinger's approach compares to dedicated forex VPS providers for multi-broker setups.