MQL5 Community Authorization Failed on VPS – Market Inaccessible, 4 Days of Troubleshooting, No Support Response

[SGA]

Hello MetaQuotes Support Team, Administrators and MQL5 Community,

I am writing here because I have been struggling with a serious MQL5 Community and Market connectivity problem for the past four days, and I have still not received a working solution from technical support. My latest communications have remained unanswered.

I have purchased several Expert Advisors from the MQL5 Market, but I cannot download, activate or use them on my second VPS because the MetaTrader 5 terminal cannot connect to MQL5 Community or Market.

This is extremely frustrating, especially because I have paid for these products and need them for my automated trading setup.

1. My setup

I use:

• A personal Windows laptop.

• A first Contabo Windows VPS.

• A second Contabo Windows VPS (Cloud VPS 8), which is the affected server.

• MetaTrader 5, currently build 6314.

• The same MQL5 Community account on all devices.

My MQL5 login works correctly on my laptop and first Contabo VPS. It fails only on the second VPS.

The username and password are correct and have been tested repeatedly.

2. Errors in MetaTrader 5

The Journal repeatedly displays:

MQL5.community: authorization failed

MQL5 Market: failed connect to server

MQL5 Market: failed to load products

Meanwhile, the terminal successfully connects to my Global Prime trading account, receives live market prices and synchronizes my positions.

Therefore, the broker connection works, while MQL5 Community and Market services fail.

3. Troubleshooting performed over four days

Together with technical assistance, I have performed extensive troubleshooting, including:

1. Verified my MQL5 username and password on multiple devices.

2. Repeatedly attempted Community authorization inside MT5.

3. Tested different MetaTrader 5 installations, including MetaQuotes, Global Prime and PU Prime.

4. Confirmed that the PU Prime MT5 installation can connect to my Global Prime trading account.

5. Observed that MetaQuotes and Global Prime installers repeatedly display a Proxy Server configuration window and fail to complete installation.

6. Checked MT5 proxy settings and confirmed that no proxy is enabled.

7. Checked Windows Internet Options, LAN proxy settings and automatic configuration settings.

8. Investigated Windows Firewall outbound rules.

9. Tested DNS resolution and HTTPS connectivity.

10. Tested connectivity to www.mql5.com over port 443 using PowerShell and curl.

11. Received HTTP 200 OK from www.mql5.com.

12. Verified TCP connectivity to remote IP addresses observed in MT5 network activity, including 194.164.179.28 and 66.203.112.227 on port 443.

13. Used Windows Resource Monitor to inspect active MT5 network connections.

14. Checked TLS-related settings and certificate-revocation behavior.

15. Checked the Windows hosts file and WinHTTP proxy configuration.

16. Checked Windows Defender and security settings.

17. Verified and synchronized Windows date and time.

18. Corrected the Windows time zone to Sofia (UTC+02:00).

19. Investigated IPv6 configuration, DNS AAAA records and routing.

20. Confirmed that the VPS has no usable default IPv6 route and that an IPv6 HTTPS connection fails.

21. Changed Windows address-selection priority to prefer IPv4.

22. Restarted MetaTrader 5 and tested MQL5 authorization again.

None of these steps resolved the issue.

4. Complete VPS reinstallation and IP address replacement

I also contacted my VPS provider, Contabo.

My second VPS originally used:

Old IP: 173.212.233.63

Contabo performed a complete Windows reinstallation and assigned a new public IP address:

New IP: 185.176.252.21

This meant starting again with a freshly installed Windows environment.

The exact same MQL5 Community and Market errors continued after the complete reinstallation and IP address change.

This is an important detail: the problem persisted across two IP addresses and a fresh Windows installation.

5. The problem is specific to MQL5 services

My MetaTrader 5 terminal successfully:

• Connects to my broker.

• Authenticates my trading account.

• Receives live price quotes.

• Synchronizes open positions.

• Checks for terminal updates.

However, it cannot authenticate with MQL5 Community or load MQL5 Market products.

The terminal reports that it is using the latest version, yet the Market remains inaccessible.

6. Lack of effective technical support

I have already contacted MQL5 technical support and submitted diagnostic information, including terminal logs.

Despite spending four days troubleshooting, I still have no resolution. I am also no longer receiving useful responses to my follow-up messages.

I have also contacted Contabo and cooperated with their troubleshooting process, including a complete VPS reinstallation.

As a paying MQL5 Market customer, I urgently need assistance accessing the Expert Advisors I have already purchased.

7. Questions for MetaQuotes developers and administrators

Could someone from MetaQuotes please investigate and clarify the following?

1. Is there a known MQL5 Community or Market authentication problem affecting certain Windows VPS environments?

2. Could MQL5 authentication or Market services be rejecting certain hosting-provider IP ranges or server environments?

3. Are there additional MQL5 authentication endpoints or services that should be tested beyond www.mql5.com?

4. Could this issue be related to a recent MetaTrader 5 build, an authentication mechanism or a server-side restriction?

5. Is there a way for MetaQuotes to examine the failed authorization attempts and determine the actual reason for rejection?

6. How can I access and activate my legitimately purchased Expert Advisors while this issue remains unresolved?

I am willing to provide additional technical logs and diagnostic results privately to the MetaQuotes support team.

I am not requesting free products or additional activations. I simply need to use the Expert Advisors that I have already purchased.

Please escalate this issue to a MetaQuotes developer or technical specialist who can investigate the authentication failure.

After four days of testing, a complete Windows reinstallation and a public IP address change, I believe this issue requires a more detailed technical investigation rather than repeating basic troubleshooting steps.

Thank you in advance to anyone who can help.

Best regards,

Stanimir Aleksandrov

[Alain Verleyen]

Do you have an open ticket on the ServiceDesk ? Please show it's number.