Customer Story: RDP Security and Auto-Start for MetaTrader 5 on a Basic Plus Windows VPS

"I have a Windows Server VPS hosting MetaTrader 5 and a Python-based automated trading system. I would like to secure remote access and enable unattended application recovery after a Windows reboot. Before changing any configuration, could you please confirm the following."

Submitted by user "a***@****.com" · Support ticket, October 20, 2026

Application Scenario

The customer runs MetaTrader 5 (MT5) together with a Python application that automates trading, on a Basic Plus Windows VPS that stays online around the clock. A MetaTrader 5 VPS like this has to meet two needs at once. The first is RDP security: only trusted IP addresses should be able to reach the server by Remote Desktop (RDP). The second is automatic recovery: MT5 and the Python application must come back on their own after any Windows reboot.

Before touching the firewall or login settings, the customer opened a support ticket. A careful MT5 VPS setup always includes a way back, and this ticket was about confirming that one exists.

Server Specifications

✅ Plan: Basic Plus Windows VPS
✅ CPU: 6 CPU Cores
✅ RAM: 12GB
✅ Storage: 180GB SSD
✅ Operating System: Windows Server
✅ Backup: Scheduled VHD backups (every 4 weeks)
✅ Workload: MT5 VPS hosting for MetaTrader 5 and a Python automated trading application, running 24/7

The Challenge

The customer wanted to harden the server and automate recovery, but each step of this MT5 VPS setup carried a risk on a live trading machine:

  • A Windows Firewall or NLA change could block RDP and cut off access entirely.
  • Their plan did not include snapshots, so there was no one-click way to undo a bad change.
  • Restarting after an update or crash meant someone had to sign in manually before MT5 and the Python application would run again.
  • They did not want to enable Administrator autologon.

They asked four specific questions and finished with one request: recommend the safest approach for this VPS.

Original support ticket question from the customer, submitted October 20, 2026

The original ticket as submitted by the customer.

Support Timeline

Date and time (2026) Event
Oct 20, 20:41 Customer submits the ticket with four questions
Oct 21, 01:43 Jay, Support Department, a human support expert, replies to all four questions and adds a recommended setup
Oct 23–26, 04:30 The system sends daily follow-ups asking whether further help is needed

The first reply arrived about five hours after the ticket was opened. As of October 26, 2026, the ticket records no further question from the customer.

What the Customer Asked and How We Answered

1. If an NLA or firewall change blocks RDP, can support restore access?

Answer: Yes. Support restores access from the host node, without reinstalling Windows or losing data. Recovery usually takes under an hour, depending on the current support queue. Technical support is available 24/7 by ticket or live chat.

2. Can RDP be limited to approved IP addresses or a VPN?

Answer: Yes. The most practical option for RDP security is an inbound rule in Windows Firewall with Advanced Security that allows the RDP port only from approved IPs or VPN. This is independent of the general Windows Firewall profile settings, and the customer controls it directly. If network-level restrictions are also wanted, the customer can send the approved IP addresses and ask support to apply them.

3. Can a backup be restored if a change goes wrong?

Answer: Yes, to the last scheduled backup. Scheduled VHD backups run every 2 or 4 weeks depending on the plan. To restore, contact support, and we restore the server from the most recent available backup. A restore takes about 2 to 4 hours depending on data size and is free of charge.

Because backups run on a schedule, a restore returns the server to the last backup point, and anything changed afterwards is lost. For that reason, support recommended taking a personal backup before making changes, such as a full system image or an export of the MT5 and Python configuration.

4. Can MT5 and Python start automatically after a reboot without Administrator autologon?

Answer: Yes. Create a separate, dedicated Windows user that has only the permissions needed to run MT5 and the Python application, and configure AutoLogon for that account. Then place shortcuts for both applications in the Startup folder:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

This is safer than Administrator autologon, and the interactive session and Startup applications still launch after every reboot. Step-by-step guide: How to auto-start an application after Windows restart.

Jay's recommendation for a safe MT5 VPS setup, in order:

  1. Take your own system image, or export your MT5 and Python configuration, before changing anything.
  2. Create a dedicated non-admin Windows user for MT5 and the Python application.
  3. Configure AutoLogon for that account instead of Administrator.
  4. Add the MT5 and Python shortcuts to the Startup folder, then reboot once to confirm both start without a manual login.
  5. Restrict your RDP port to approved IPs or VPN in Windows Firewall. Keep your current session open while you test a second connection.
  6. Keep support's contact details handy. If RDP access is ever lost, open a ticket or live chat and we restore access from the host.

Key Takeaways for MetaTrader 5 VPS Users

  • Ask before you change. Confirming the recovery path first turns a risky change into a routine one.
  • A scheduled backup is not a snapshot. VHD backups run every 2 or 4 weeks, so create your own image before editing firewall, login or startup settings.
  • Avoid Administrator autologon. A dedicated non-admin account with only the permissions MT5 and Python need still gives you unattended restarts.
  • Apply RDP security last. Set up AutoLogon and Startup first, test a reboot, and then add the IP restriction so a typo cannot lock you out mid-setup.
  • A Windows VPS for MT5 keeps recovery simple. The terminal runs on Windows, so auto-start, login and firewall rules all use standard Windows tools: AutoLogon, the Startup folder and Windows Firewall.
  • Capacity was not the issue. Our sizing table supports up to 5 forex terminals on a 6vCores 12GB VPS. This customer's question was about safety and recovery, not performance.

What This Case Shows About Our Support

Good MT5 VPS hosting is about more than CPU and RAM. It also depends on what happens when a setting goes wrong at 3 a.m.

  • A real person answered. The ticket was handled by a human support expert, with the agent's name and timestamps on record.
  • Every question got a direct answer. Recovery, firewall, backup and auto-start were each answered separately, with expected duration and cost where relevant.
  • Recovery does not mean reinstalling. Host-level access restoration keeps Windows and your data intact.
  • Support is always available. Technical support runs 24/7 through ticket and live chat.

Deploy Your Own Version of This MT5 VPS Setup Now?

Basic Plus Windows VPS for MT5

  • CPU: 6 CPU Cores
  • Memory: 12GB RAM
  • Disk: 180GB SSD
  • OS: Windows Server
  • Location: USA (Dallas, TX or Kansas City, MO)
  • Backup: Scheduled VHD backups

$25.99/mo

Order Now

Need more MT5 VPS? See our MT5 VPS Page.

Last Updated: 10/27/2026

Last Updated:   10/27/2026
Outline