VPS security for traders

Keep your trading VPS safe: one login per person, investor passwords for sharing, 2FA where offered, a locked-down RDP and careful installs.

  • Beginner
  • Admin RDP · Windows VPS
  • 3 min read

By RunRacks Team · Published

Whoever can sign in to your VPS can use the trading terminals running on it. That makes the VPS as valuable as your broker login. These steps protect it without making daily use harder.

1. One person, one login

  • Never share your RDP username and password, not with signal providers, EA sellers or "account managers". Anyone with RDP access can place trades, change your EAs or copy your files.
  • If someone genuinely needs to look, share read-only access to the trading account instead: MetaTrader supports an investor password that can view the account but not trade.
  • If a second person must use the server, give them their own Windows account: Create Windows users with Remote Desktop access.

2. Strong, unique passwords everywhere

Use different long passwords for the VPS, the RunRacks client area, your email and your broker account, and keep them in a password manager. See Change your Windows server password safely.

3. Turn on two-factor authentication where it is offered

Two-factor authentication (2FA) is set up with each service, not on the VPS. Turn it on for your email account (it can reset everything else) and for your broker's client portal if your broker offers it.

4. Lock down Remote Desktop

Follow Secure Remote Desktop on Windows Server: keep Network Level Authentication on, set an account lockout policy, and limit RDP to your own IP addresses if they are stable.

5. Be careful what you install

  • Download MetaTrader from your broker or MetaQuotes, and EAs only from sources you trust.
  • Never run "cracked" EAs or indicators. They are a common way to hide malware that steals logins.
  • Keep Microsoft Defender on (guide) and Windows updated (guide).

6. Keep the server for trading

Avoid using the trading VPS for general browsing, email attachments or downloads. The less you do on it, the less can go wrong. If you also want a desktop for everyday work, keep that separate.

7. Protect the devices you connect from

Your laptop and phone hold saved RDP connections. Use a screen lock on each, keep them updated, and do not save the RDP password on shared computers.

If you think someone got in

  1. Change the Windows password from a session you control: net user Administrator *.
  2. Change your broker password and check recent trades and withdrawals with your broker.
  3. Check Event Viewer → Security for successful logins (event ID 4624, logon type 10 is Remote Desktop).
  4. Open a support ticket with the times you noticed anything unusual.

Next steps

Was this guide helpful?

Still stuck?

Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.

Security

Check the Windows Firewall rule for RDP port 12230

Find and verify the inbound TCP 12230 rule that lets Remote Desktop reach your RunRacks server, recreate it if it was deleted and scope it without locking yourself out.

  • Intermediate
  • Windows VPS · Admin RDP
  • 5 min read

Security

iptables basics: list, allow, drop and save rules

Learn how iptables chains and rule order work, then build a small ruleset that allows SSH and web traffic, drops everything else and can be edited by line number.

  • Intermediate
  • Linux VPS
  • 6 min read