MQL5.community authorization + LiveUpdate suddenly fail on a datacenter server — same account works fine from home

New comment
 
Hi all,

Hoping a moderator or someone with experience can help me understand a sudden change.

Setup: a few MetaTrader 5 terminals on a dedicated server (a datacenter IP). Since 2026‑08‑29 at ~10:27 UTC, all terminals suddenly can no longer authorize with MQL5.community, and MT5 LiveUpdate fails too. The broker/trade‑server connection and trading itself
keep working normally — only MQL5.community / Market / LiveUpdate are affected.

What I have already verified:
- It started suddenly and simultaneously on all terminals, with no restart, no update and no config change on my side (the terminals had been running continuously for weeks).
 The same MQL5 account works perfectly from my home (residential) connection, even on an older terminal build → so it is not the account, password or build.
- The network path is healthy: TCP to mql5.com:443 connects and completes a TLS 1.3 handshake, and the terminal keeps an established connection to your infrastructure. The authorization is rejected at the application level, not a firewall/connectivity problem on my
side.
- The server IP is not on any public blocklist (Spamhaus / Barracuda / SpamCop / DroneBL).

Journal (identical on all terminals, account name masked):
2026.08.23 18:13    MQL5.community   activated for 'XXXX'    <- last success
2026.08.29 10:27:37 MQL5.community   authorization failed    <- first failure
2026.08.29 12:26:45 MQL5.community   authorization failed
2026.08.29 12:26:45 Virtual Hosting  failed to get list of virtual hosts [1003] (raw - read failed, 0 wsa error, 1 bytes needed)
Terminal build: 6140.

My questions:
1. Is MQL5.community / Market / LiveUpdate access restricted for datacenter / hosting IP ranges, and did something change around 2026‑08‑29 10:27 UTC?
2. If it is an IP‑based restriction, how can it be lifted for a legitimate single‑owner server?
3. Has anyone else seen community and LiveUpdate fail from a VPS/dedicated server while the same account works fine from a home connection?

I’m happy to share the exact IP and full Journal privately with a moderator. Thanks!
 

Since its the weekend, this may be temporary, try again later.

Also check your MQL5.com IP settings, then restart your server and try again.

https://www.mql5.com/en/users/flyrain/security

 

Since every terminal failed at the same time behind one public IP while the same account still works from home, I’d isolate the IP first. Test one terminal through a different outbound IP or mobile hotspot. If authorization works again, send the server IP, UTC timestamps, terminal build and Journal entries privately to Service Desk. Public blocklists won’t show an internal MQL5 security restriction.

New comment