Connection to XXXX lost - OVH Canadá Servers

New comment
 
Hello,


We are a VPS Hosting Platform, and most of our clients use our services to run MT5, across several different brokers. Recently we have identified that there is a communication problem between our datacenter and MT5. We are suspecting a blockage on the Metaquotes servers.


It seems that the MT4 servers work perfectly on our network, but MT5 cannot connect.

I believe that it may be a blockage at the ASN level, or something like that.

We use OVH servers in our infrastructure. 

Is anyone else experiencing this issue? Is there a contact where I can request technical support for MT5?

Hello,


After much investigation, we noticed that our customers who use Windows Server 2016 VPS are unable to use MT5 after the Build 4866 update.

We are having to switch them to Windows Server 2019.

Is there any possibility of checking if there is in fact a bug with MT5 Build 4866 and Windows Server 2016? Or is it the lack of an OS update?

 

You need to contact Service Desk.


NOTE-1: The Forum is mainly for users to:

(i) exchange ideas

(ii) discuss trading strategies, market trends, MetaTrader features and coding tips

(iii) share views on other trading-related and market-related topics.


NOTE-2: We’re all regular users, so we don’t have direct access to the Service Desk or their response timelines.

 
Hello,

After much investigation, we realized that the problem is actually occurring only on Windows Server 2016. And it started occurring after the most recent update (Build 4866). I believe it is a bug with the Windows Server 2016 operating system.

We are updating customer machines to Windows Server 2019. This resolves the issue.

In the meantime, we need a position regarding this bug, introduced in Build 4866.
 

It sounds to me as if MQ no longer wants to/can no longer guarantee support for operating systems that are too old in order to further develop the terminal in terms of speed, multi-threading, optimisation and use of the features of the latest CPUs and GPUs.
But I have no inside view on this.

If that is the case, there will be no workaround, just a more modern OS from the VPS provider.

Anyway, thanks for this information!

 
Yohan Lopes #:
Hello,

After much investigation, we realized that the problem is actually occurring only on Windows Server 2016. And it started occurring after the most recent update (Build 4866). I believe it is a bug with the Windows Server 2016 operating system.

We are updating customer machines to Windows Server 2019. This resolves the issue.

In the meantime, we need a position regarding this bug, introduced in Build 4866.

there is several issues with mt5 compatability with server 2016. compatability issues between server 2016 and mt5 are not a new thing. just 1 such issue that occurs when running multiple terminals of mt5 -- while on 2016 -- already started happening in '23; discussed here

So compatability issues between mt5 and server 2016 are not new; AND the occurance of new issues tells me that developers dont care.

And frankly, atho I still love and use that server version on my home system, the newer versions of server are far superior despite all of the bloat that is put on just the client flavours of them.

New versions of mt are already pushed onto your vps clients; so I think that your vps clients will just take this new "forced upgrade" -- "on the chin" and may even thank you for your obvious help and support.

 
Michael Charles Schefe #:

there is several issues with mt5 compatability with server 2016. compatability issues between server 2016 and mt5 are not a new thing. just 1 such issue that occurs when running multiple terminals of mt5 -- while on 2016 -- already started happening in '23; discussed here

So compatability issues between mt5 and server 2016 are not new; AND the occurance of new issues tells me that developers dont care.

And frankly, atho I still love and use that server version on my home system, the newer versions of server are far superior despite all of the bloat that is put on just the client flavours of them.

New versions of mt are already pushed onto your vps clients; so I think that your vps clients will just take this new "forced upgrade" -- "on the chin" and may even thank you for your obvious help and support.


I have connectivity issues with server 2019 so something else is the issue

 
Ricardo Dacosta #:


I have connectivity issues with server 2019 so something else is the issue

then, your issue has nothing to do with this thread. you need to create your own thread. Moderators will chastise you for hijacking other persons messages and either delete your post soon, OR force you and your post to a thread called "unrelated issues".

 
Yohan Lopes:
Hello,


Did you see the thread for 4866? It seems that others using 4866 and on other windows versions have same issues. I think that you should create a post there too.

 

Could you provide list of IP addresses, please?

Nothing wrong with terminal or versions.

 
@MetaQuotes #: Could you provide list of IP addresses, please? Nothing wrong with terminal or versions.

Could you check if my VPS provider has been banned?  185.231.71.244

I had created a thread but somehow got removed. 

 
@Ricardo Dacosta #: I had created a thread but somehow got removed. 

I did find your topic "Unable to connect to terminal past 48 hours", posted 5 days ago, via a Google search, but the link is no longer valid.

I do remember seeing it, but none of the moderators removed it, and it is also not currently in any of our system records.

It must have been deleted due to a system malfunction during a maintenance cycle.

According to the Google preview text, the post started as follows:

"Not sure what may have changed but I am unable to connect to my broker's terminal in the past 48 hours. I am operating on a Windows 2019 VPS."

12
New comment