FXVPS
Get Started
forex vps troubleshooting support

Navigating Technical Issues: Troubleshooting Your Forex VPS

person
FXVPS
Share
Navigating Technical Issues: Troubleshooting Your Forex VPS

Most VPS issues have straightforward fixes that take under five minutes. This guide covers the five problems FXVPS support handles most frequently, with the exact error messages you’ll see, what they mean, and how to resolve them yourself before opening a ticket.

Problem 1: Cannot Connect via RDP

This is the most common support request, and it almost always comes down to one of four causes.

Check Your VPS IP and Port

FXVPS uses port 41011 for RDP connections, not the default 3389. When entering your connection details in Remote Desktop Connection, the format should be:

💡 Tip: FXVPS uses port 41011 for RDP instead of the default 3389. Always enter your connection as IP:41011 — omitting the port will cause the connection to time out.

123.45.67.89:41011

If you leave off the port number, your RDP client tries port 3389, gets no response, and times out. Double-check the IP address and port in your FXVPS welcome email.

Check If the VPS Is Running

Open a command prompt or PowerShell on your local machine and run:

ping 123.45.67.89

Replace with your actual VPS IP. If you get replies like Reply from 123.45.67.89: bytes=32 time=45ms TTL=118, the VPS is online and the issue is likely with the RDP service or your local network. If you get Request timed out or Destination host unreachable, the VPS may be down or there is a network routing issue. For more on using ping to diagnose connectivity, see our guide on how to check if a forex VPS is online with ping.

Check Your Local Firewall

Corporate networks, hotel WiFi, and some ISPs block outbound RDP traffic. If ping works but RDP doesn’t connect, your local firewall or network may be blocking port 41011. Try connecting from a different network (mobile hotspot works well as a test) to rule this out.

Common RDP Error Messages

“Remote Desktop can’t find the computer” — This means the IP address is wrong, the VPS is powered off, or there’s a DNS resolution failure. Verify the IP address character by character against your welcome email.

“Your credentials did not work” — The password is wrong. This is the number one cause. Copy and paste the password directly from your welcome email rather than typing it. Watch for extra spaces that sometimes get copied before or after the password. Also make sure you’re using the correct username — FXVPS uses specific usernames listed in your provisioning email.

“The remote session was disconnected because there are no Remote Desktop License Servers available” — This is a server-side licensing issue that you cannot fix yourself. Contact FXVPS support and we’ll resolve it, typically within minutes.

“An internal error has occurred” — Usually caused by a stale RDP session. Open Remote Desktop Connection, click “Show Options,” go to the “Experience” tab, and uncheck “Persistent bitmap caching.” Try connecting again.

Problem 2: MT4 or MT5 Shows “No Connection”

When MetaTrader shows “No connection” or “Common Error” in the bottom-right status bar, your trading platform can’t reach the broker’s server.

Step-by-Step Fix

  1. Check the Journal tab in MT4/MT5 (Ctrl+T to open the Terminal panel, then click “Journal”). Look for specific error messages. Common ones include “no connection to [server name]” or “connection to [server] lost.”

  2. Right-click your account in the Navigator panel and select “Rescan servers.” This forces MT4/MT5 to re-query all available servers and pick the fastest one.

  3. Restart MT4/MT5 entirely. Close the application and reopen it. A fresh start resolves most transient connection issues.

  4. Check if the broker is under maintenance. Many brokers perform server maintenance over the weekend or during rollover time (around 5 PM EST / 10 PM GMT). Check your broker’s website or contact their support.

  5. Verify the server address hasn’t changed. Some brokers periodically update their server addresses. Log into your broker’s client portal and compare the listed servers with what’s configured in your MT4/MT5.

If none of these work, open a command prompt on the VPS and ping your broker’s server IP. If the ping fails, there may be a routing issue between the datacenter and the broker — contact FXVPS support with the broker server name and we’ll investigate. You can extract your broker’s server IP to test connectivity directly.

💡 Tip: Run ping broker-server-ip -n 100 from both your home PC and your VPS, then compare results. The difference in average latency shows you exactly how much execution speed you’re gaining.

Problem 3: EA Stopped Trading

Your Expert Advisor was working yesterday, but today it’s sitting idle with no new trades. This is almost always a configuration issue, not a VPS problem.

The AutoTrading Button

Look at the toolbar in MT4/MT5. The “AutoTrading” button should show a green play icon. If it shows a red stop icon, automated trading is globally disabled. Click it once to re-enable. This button gets toggled off if the platform restarts and the setting wasn’t persisted.

EA Properties Check

Right-click the EA on your chart, select “Properties,” and go to the “Common” tab. Confirm that “Allow automated trading” is checked. Also verify “Allow DLL imports” is checked if your EA requires external DLL libraries.

Reading the Experts Tab

The Experts tab (next to Journal in the Terminal panel) shows messages from your EA. Common error messages and their meanings:

  • “Trade context busy” — Another EA or script is trying to trade at the same time on the same account. MT4 only allows one trade operation at a time. If you’re running multiple EAs, stagger them or use an EA that handles trade context locking.

  • “Not enough money” (error code 134) — Your account balance or free margin is too low to open the requested position. Either reduce lot size in the EA settings or deposit more funds.

  • “Trade is disabled” (error code 133) — Trading is disabled for your account on the broker side. This can happen if the market is closed, your account is in margin call, or the broker has restricted your account.

  • “Invalid stops” (error code 130) — Your stop loss or take profit is too close to the current price. The broker has a minimum stop distance, and your EA is placing orders inside that range.

  • “Off quotes” (error code 136) — The price changed between when the EA requested it and when the order was submitted. This usually resolves itself on the next tick.

Problem 4: VPS Running Slow

If your VPS feels sluggish — delayed keystrokes in RDP, MT4 charts loading slowly, or general unresponsiveness — the cause is usually high resource usage.

Diagnose with Task Manager

Press Ctrl+Shift+Esc to open Task Manager. Click “More details” if it opens in compact mode, then check the Performance tab.

If RAM is above 90%: You’re running out of memory. Click the “Processes” tab and sort by Memory to see what’s consuming the most. Common culprits are multiple MT4/MT5 instances, Chrome with many tabs open, or third-party indicators that load large data sets. Close unnecessary programs. If you consistently need more RAM, consider upgrading from the Core plan ($29/mo, 2GB RAM) to the Pro plan ($39/mo, 4GB RAM) or the Scaling plan ($79/mo, 8GB RAM).

💡 Tip: Each MT4 terminal uses 300-600MB of RAM; MT5 uses 600MB-1.2GB. Add 1.5GB for Windows overhead, then pick a plan with at least 20% headroom to handle tick-data spikes during high-volatility sessions.

If CPU is above 80% consistently: Check what process is using the CPU. Windows Update is a frequent offender — the TiWorker.exe or svchost.exe process can spike CPU usage to 100% during update downloads and installations. If you see this, let it finish or reschedule updates for off-hours.

If disk usage is at 100%: This usually indicates Windows is performing background tasks like indexing, antivirus scanning, or applying updates. Wait 10-15 minutes. If it persists, check for processes like SearchIndexer.exe and consider disabling Windows Search if you don’t use it on your VPS.

RDP Latency vs VPS Performance

Slow RDP can also be caused by a poor internet connection on your end, not the VPS itself. To distinguish: if everything inside the VPS runs fine (EAs execute instantly, charts update in real time) but the screen feels laggy to interact with, the issue is your internet connection to the VPS, not VPS performance. Try lowering the RDP color depth or resolution in your Remote Desktop Connection settings under “Display.”

Problem 5: Windows Update Restarted the VPS

You wake up to find your VPS rebooted overnight. Your EAs were stopped, and you missed hours of trading. This is the most frustrating issue traders encounter.

Prevention: Set Active Hours

On the VPS, go to Settings > Update & Security > Windows Update > Change active hours. Set your active hours to cover your trading session. Windows will not restart during these hours. For 24/5 forex trading, set active hours to start Monday morning and cover as much of the trading week as possible.

⚠️ Warning: Windows auto-restart is the #1 killer of unattended EAs. Disable it via Group Policy (gpedit.msc) immediately after setting up your VPS — before you attach a single EA.

Recovery: Auto-Start Your EAs

Even with active hours configured, restarts can still happen. Set up your MT4/MT5 to start automatically after a reboot:

  1. Press Win+R, type shell:startup, and press Enter. This opens the Startup folder.
  2. Copy a shortcut to your MT4/MT5 terminal into this folder.
  3. In MT4/MT5, make sure your EA is attached to a chart template saved as default, so it reloads automatically when the platform starts.

This way, even if a restart occurs, your platform relaunches and your EAs resume within a minute or two.

Using Event Viewer to Investigate

When something went wrong and you’re not sure what happened, Event Viewer is your forensic tool.

  1. Press the Windows key, type “Event Viewer”, and open it.
  2. In the left panel, expand Windows Logs > System. Look for events with source “User32” and Event ID 1074 — this tells you what initiated a restart and when.
  3. Check Windows Logs > Application for crash events. Filter by “Error” level to see application crashes that may have affected your trading platform.
  4. A “Source: EventLog, Event ID 6008” entry means the system shut down unexpectedly (crash or power issue rather than a clean restart).

This information helps FXVPS support diagnose whether the restart was caused by Windows Update, a system crash, or a hardware event.

When to Contact FXVPS Support

Handle these yourself: RDP connection typos, MT4 configuration, EA settings, running too many programs, Windows Update settings.

Contact support for: persistent network connectivity issues that survive VPS restart, RDP licensing errors, suspected hardware problems (frequent unexpected reboots, disk errors in Event Viewer), or any issue you’ve spent more than 15 minutes troubleshooting without resolution.

FXVPS provides 24/7 support with typical response times under 30 minutes. When submitting a ticket, include the specific error message, when the problem started, and any troubleshooting steps you’ve already tried — this helps us resolve your issue faster.