Common issue categories
MetaTrader problems often look similar to users, but the cause may sit in a different layer: credentials, server selection, account status, internet connection, platform settings or broker-side configuration.
- Incorrect login ID, password or investor password
- Wrong trading server selected during login
- Account not enabled, archived or restricted
- Unstable connection or firewall limitation
- Outdated desktop or mobile platform version
- Indicator, Expert Advisor or chart configuration issue
What each category usually means
Credentials: The login ID, master password or investor password was typed incorrectly, copied with a stray space, or reset by the broker. Triage starts by confirming the exact ID and asking the client to retype the password manually rather than pasting.
Server selection: Brokers run multiple servers (demo, live, different regions). Selecting the wrong one produces an "invalid account" or "no connection" error even when credentials are correct. The fix is to confirm the server name from the broker's welcome email or client portal.
Account state: The account may be inactive, archived, under review, or blocked pending verification. Only the broker can change account status, so this is always an escalation item — but documenting it early prevents a long troubleshooting loop.
Connectivity: Local firewalls, VPNs, corporate networks or unstable mobile data can block the MetaTrader port. Asking the client to try a different network quickly isolates a local-connection cause from a platform-side one.
Platform version: An outdated terminal may fail to connect or display data correctly. Confirming the build number and prompting an update resolves a surprising share of "suddenly stopped working" reports.
Indicators and EAs: A misbehaving custom indicator or Expert Advisor can freeze charts or block execution. Disabling EAs and reloading a clean chart template helps isolate the cause.
Common MT4 and MT5 error messages and what to check first
The cards below list the MetaTrader error messages support teams see most often, the typical cause, and the first thing to verify before escalating. Support agents should capture the exact message text and confirm the corresponding check before sending the ticket to a broker or developer.
Pre-escalation checklist for support agents
Before sending a MetaTrader issue to a broker, developer or compliance team, a support agent should be able to answer yes to every item below. A complete pre-escalation check reduces repeat contacts and shortens resolution time.
- Is the correct broker server selected and confirmed?
- Have credentials been retyped manually (not pasted)?
- Is the terminal updated to the latest build?
- Has a different network or device been tested?
- Is the exact error text captured with a screenshot?
- Have indicators and EAs been disabled to rule them out?