An mt4 vps keeps MetaTrader 4 and your Expert Advisor running when your home computer is off, asleep, or disconnected. This guide shows you how to choose the right Windows VPS, move your EA and settings, enable automated trading, recover after a reboot, and check that the terminal is actually connected.
Why run MT4 on a VPS?
Your EA needs the MT4 terminal to stay open and connected to the broker. A Windows VPS gives the terminal a separate always-on environment, so your home internet connection and laptop do not have to remain active.
VPSLake describes Buffalo as low-latency for NY4 brokers, with about 12–13 ms to listed Equinix NY4 servers. It starts at $9.99/mo and includes full Administrator access and a dedicated US IPv4; Windows is BYOL.
What you need before you start
Prepare these items before ordering or connecting:
- Your broker’s MT4 installer or download link.
- Your broker account number, password, and exact server name.
- The EA file, usually
.ex4or.mq4, its.setpreset, and any custom indicators, libraries, or templates. - A demo account for testing, plus a Windows VPS sized for your number of terminals and charts.
For one MT4 terminal and one EA, the 4 GB Buffalo plan is a practical starting point. See VPSLake’s MT4 and MT5 VPS requirements guide for sizing details.
Step 1: Choose the VPS location and Windows image
Why this matters: the location affects the network path between MT4 and your broker, while the image determines the desktop you will administer.
- Ask your broker which data-center location hosts the account’s MT4 server. If it is an NY4-hosted server, Buffalo is the VPSLake option positioned for that use case.
- Select a Buffalo Windows plan with enough reserved RAM and CPU for your terminals. The 4 GB plan has 3 vCPU and 4 GB reserved RAM; the 8 GB plan is a better fit for several MT4 terminals.
- On the order form, choose the Windows Server 2019, Windows 10 Pro, or Windows 11 Pro image that fits your workflow.
- Remember that Windows is BYOL: VPSLake supplies the image, but you bring your own Windows licence. There is no Windows licence surcharge.
- Complete the order and wait for the server credentials. Setup is automatic after payment; the client area provides console, reinstall, reboot, and password-reset controls.

Success looks like: you can reach the Windows desktop by RDP, know which broker server you will use, and have a plan sized for your terminal count.
Step 2: Connect to Windows and install MT4
Why this matters: MT4 must be installed inside the VPS, not left on your personal computer, for the EA to continue running after you disconnect.
- Open Remote Desktop Connection on your computer, enter the VPS IP address, and sign in with the supplied Windows credentials.
- Download the MT4 installer from your broker or another source you trust. Install the terminal on the VPS and allow it to open after installation.
- If you need separate broker accounts at the same time, install each MT4 copy in a different directory. MetaTrader does not support multiple terminals running from the same directory simultaneously.
- Open MT4 and select File → Login to Trade Account. Enter the account number, password, and the correct broker server.
- Wait for prices to populate in Market Watch, then check the account number and server before adding any EA.
MetaTrader stores user files separately from the installation. Its Terminal Start and Data Structure documentation explains why File → Open Data Folder finds the correct directory.
Success looks like: MT4 shows live quotes, the intended account is logged in, and the terminal opens without an authorization or server error.
Step 3: Move your EA, indicators, and settings
Why this matters: copying files into the installation folder can put them in the wrong place; the terminal’s data folder is the location MT4 reads for user programs.
- In the VPS terminal, select File → Open Data Folder.
- Open the
MQL4folder and copy each file type into its matching location:
| File | Destination |
|---|---|
EA files: .ex4 or .mq4 | MQL4\Experts |
| Custom indicators | MQL4\Indicators |
Preset files: .set | MQL4\Presets |
| Required libraries | MQL4\Libraries |
Templates: .tpl | templates |
- Close and reopen MT4, or refresh Expert Advisors and Indicators in Navigator.
- Open the chart and symbol your EA expects. Pay attention to broker suffixes such as
EURUSDm; the symbol name must match the one used in the EA settings. - Drag the EA from Navigator onto the chart. Load the vendor’s
.setfile, if supplied, and review every input.
Do not copy an unchecked EA. If it needs DLL access or external URLs, enable only the specific permission and trusted URL documented by its developer.
Success looks like: the EA appears under Navigator, its inputs are present, and the correct chart shows the EA name after you attach it.
Step 4: Enable AutoTrading and attach the EA
Why this matters: an EA can be visible and calculating while still being blocked from sending trade operations.
- Select Tools → Options → Expert Advisors.
- Enable Allow automated trading. Keep the account-change, profile-change, and symbol/timeframe safeguards enabled unless you have a specific reason to change them.
- Click the AutoTrading toolbar button so it is enabled.
- Open the EA properties on the chart. In Common, enable Allow live trading when you are ready to use that account. Review the Inputs tab and click OK.
- If the EA uses
WebRequest(), add only its documented URLs. Enable Allow DLL imports only for a trusted EA; MetaTrader recommends disabling DLL imports for unknown experts.
MetaTrader’s Expert Advisors setup documentation separates the terminal-wide AutoTrading permission from the EA’s own live-trading permission. Both levels matter.
Success looks like: the AutoTrading button is enabled and the chart shows the EA name with a smiley in the upper-right corner. A letter L means live trading is disabled for that EA; a missing or warning symbol means you still have a setting to fix.
Step 5: Keep MT4 running after disconnects and reboots
Why this matters: closing your RDP connection is different from signing out, and a full Windows reboot requires a separate startup check.
- When you finish, close the Remote Desktop window or choose Disconnect. Do not choose Sign out; logging off ends the Windows user session and closes its applications.
- Create a shortcut to the correct MT4 executable. Press
Win+R, entershell:startup, and place the shortcut in the Startup folder. - For reboot recovery, open Task Scheduler and create a task triggered At log on for the Windows account that runs MT4. Set the action to start the same executable.
- Reboot the VPS once while using a demo account. Reconnect through RDP, confirm that Windows logged in, and check whether MT4 opened with the right account, charts, and EA.
- If several terminals use the VPS, give each one its own installation directory and shortcut or scheduled task.
Test the recovery path before relying on it: a reboot can expose a wrong shortcut, changed account, missing data folder, or manual EA permission.
Success looks like: after a planned reboot and sign-in, MT4 is open, connected to the intended broker account, and the EA is attached with AutoTrading enabled.
Step 6: Verify that the EA is really trading
Why this matters: an open MT4 window alone does not prove that the EA is connected, authorized, or receiving the symbols it expects.
Use this checklist after the first setup and after every major change:
- Check the account number and broker server in File → Login to Trade Account.
- Confirm that Market Watch is receiving prices and that the chart symbol matches the broker’s symbol name.
- Confirm that AutoTrading is enabled at the toolbar and under Tools → Options → Expert Advisors.
- Confirm the EA smiley and review the Experts tab for initialization messages, rejected requests, or missing files.
- Review Journal for connection and login events. MetaTrader records EA messages in Experts and stores logs under the terminal data folder.
- Disconnect from RDP, wait, reconnect, and check that the same EA and account remain active.
- Reboot the VPS with the demo account, repeat the checks, and only then use the setup for your intended account.
For a second opinion on provider choice, see VPSLake’s best cheap Forex VPS providers for MT4 and MT5. Compare the broker location, Windows requirements, and number of terminals rather than choosing on price alone.
Troubleshooting common MT4 VPS problems
The EA does not appear in Navigator
Open the data folder from inside the VPS terminal and verify that the file is in MQL4\Experts, not only in the installation directory. Refresh Navigator or restart MT4. An .mq4 source file may need to be compiled in MetaEditor.
The EA name appears but there is no smiley
Check the terminal-wide AutoTrading button, Allow automated trading, and Allow live trading in the EA’s Common tab. Inspect Experts and Journal for a missing DLL, invalid input, unavailable symbol, or authorization message.
MT4 worked until the VPS rebooted
Reconnect to Windows and confirm that the correct user signed in. Check the Startup folder or Task Scheduler target. If MT4 opens but the EA does not, verify the terminal’s data folder and AutoTrading permissions.
The EA trades twice
Close the old MT4 terminal on your home computer and duplicate terminals on the VPS. Check for duplicate charts, installations, and scheduled tasks.
FAQ
Can I run MT4 24/7 on a VPS?
Yes. MT4 can continue running on a Windows VPS while your local computer is offline, provided the terminal remains open, connected, and permitted to run the EA. Check it after reboots, updates, and login changes.
Do I need a Windows licence for an MT4 VPS?
Yes. Select the Windows Server 2019, Windows 10 Pro, or Windows 11 Pro image on the order form and bring the applicable licence; VPSLake supplies the image without a licence surcharge.
Should I disconnect or sign out of the VPS?
Disconnect from Remote Desktop so the Windows session and MT4 can remain active. Do not sign out unless you want to close that user’s applications.
How do I know my EA is working after migration?
Check the account and server, live quotes, AutoTrading, the EA smiley, and fresh Experts and Journal messages. Test a disconnect and planned reboot with a demo account first.