MQL5.community authorization failed (401) on fresh MT5 installation – same account works on VPS

[ranaasad12]

Title: MQL5.community authorization failed (401) on fresh MT5 installation – same account works on VPS

Hello everyone,

I'm experiencing a problem logging into my MQL5.community account through MetaTrader 5 on my Windows 10 laptop.

The problem:

Whenever I open MT5, I receive the following errors in the Journal:

MQL5.community authorization failed Virtual Hosting failed to get list of virtual hosts [401]

My MQL5.community username and password are correct. I can log into the MQL5 website successfully, and the same account works normally in MT5 on my VPS.

My setup:

• Operating system: Windows 10 (version 22H2)

• MetaTrader 5 build: 6302

• Fresh MT5 installation

• The error occurs even before logging into my trading account or MQL5.community account for the first time.

Troubleshooting already completed:

1. Confirmed that my MQL5 username and password work on the MQL5 website.

2. Confirmed that the same MQL5 account works in MT5 on my VPS.

3. Tested MT5 using both my normal Wi-Fi and a mobile hotspot. The problem remains.

4. Tested connectivity to https://www.mql5.com and https://www.metatrader5.com using curl. Both return HTTP 200.

5. Tested both IPv4 and IPv6 connectivity successfully.

6. Confirmed that Windows has no WinHTTP proxy configured.

7. Checked Microsoft Defender and Windows Firewall. MT5's terminal64.exe is allowed, and there are no relevant blocked events in Protection History.

8. Checked TLS settings.

9. Installed Microsoft Edge WebView2 Runtime and confirmed that its application folders exist.

10. Tried different MT5 builds, including 6292 and 6302. The issue persists.

My questions:

• Why does MQL5.community authorization fail with error 401 on my laptop when the same credentials work on my VPS and the MQL5 website?

• Could my laptop's public IP address or device be blocked by the MQL5 authorization server?

• Is there any additional MT5 log or diagnostic test that can identify the cause?

• Could this be related to a recent MT5 build or a server-side authentication issue?

I would appreciate any help or suggestions. I have spent considerable time troubleshooting this and would like to identify the actual cause rather than reinstalling MT5 repeatedly.

Thank you.

[Sergey Golubev]

It is difficult to find the reason of this issue (because there are a lot of reasons) so I am recommending to you to read this summary post about - 
post #1 and post #5