Disconnects

Created at 19 Feb 2019, 09:22

Joined 22.11.2018

Disconnects
19 Feb 2019, 09:22

Hi,

we're observing the following:

1. FxPro, 2019-2-19 3:51:44 CET, connected to h2.p.ctrader.cn. Our logs:

1.1 'the telecommunication link error is detected: closed by the counterpart'

1.2 After disconnecting and trying to login at 2019-2-19 3:51:45: 'Cannot logon: after sending the initial Logon message the telecommunication link error is detected (Connection reset by peer : System error code = 104).'

2. ICMarkets, 2019-2-19 3:50:33 CET. Our logs:

2.1 'the telecommunication link error is detected: Test Request (1) message was transmitted, but there is still no heartbeat message received after 36 seconds, so the connection is considered lost'

2.2 After disconnecting and trying to login at 2019-2-19 3:51:03: 'Cannot connect to host h59.p.ctrader.com on port 5211 : Timer expired : System error code = 62'

3. OctaFX, 2019-2-19 3:50:33 CET. Our logs:

3.1 'the telecommunication link error is detected: Test Request (1) message was transmitted, but there is still no heartbeat message received after 36 seconds, so the connection is considered lost'

3.2 After disconnecting and trying to login at 2019-2-19 3:51:03: 'Cannot connect to host h59.p.ctrader.com on port 5211 : Timer expired : System error code = 62'

Can you advise how we can handle such terminal errors?

Kind regards

@terryww2

Replies

terryww2
19 Feb 2019, 09:39

Especially concerning to us is that after such link error even after 30s we cannot reconnect as we get sys code error 104 or 62.

@terryww2

PanagiotisCharalampous
19 Feb 2019, 11:06

Hi terryww2,

Thanks for letting us know, we will investigate this.

Best Regards,

Panagiotis

@PanagiotisCharalampous

terryww2
21 Feb 2019, 08:42

Hi.

A day ago we detected such errors also for FxPro and FxPig. Any updates on that?

Kind regards

@terryww2

PanagiotisCharalampous
21 Feb 2019, 10:00

Hi terryww2,

We will be updating our proxies over the weekend. We expect this to be solved after the updates.

Best Regards,

Panagiotis

@PanagiotisCharalampous

terryww2
21 Feb 2019, 10:09

We have now logged into cTrader web and updated our connection info. We can connect to FxPro again. Seems like getting the list of your proxies from brokers and going through the list on connection error every time is the only reliable way for us to stay connected.

@terryww2

terryww2
22 Feb 2019, 14:26

We're again seeing the following link erorros with Pepperstone, connected to h35.p.ctrader.com: System error code 111, 62 and 104.

@terryww2

terryww2
22 Feb 2019, 15:55

After connecting to Pepperstone's h9.p.ctrader.com (as checked with cTrader->settings->FIX) we again get link errors:

1. 'Cannot logon: after sending the initial Logon message the telecommunication link error is detected (closed by the counterpart).'

2. 'Cannot logon: the first inbound message is not an acknowledgment Logon ( 8=FIX.4.4 9=134 35=5 49=cServer 56=pepperstone.x 34=2 50=QUOTE 57=Quote 52=20190222-13:51:10.245 58=InternalError: Authentication took too long 10=066 ).'

@terryww2

PanagiotisCharalampous
22 Feb 2019, 16:05

Hi terryww2,

As I said above, we will be updating our proxies over the weekend.

Best Regards,

Panagiotis

@PanagiotisCharalampous

terryww2
25 Feb 2019, 08:30

We can't connect to Pepperstone at all: 'Cannot logon: after sending the initial Logon message the telecommunication link error is detected (closed by the counterpart).'

@terryww2

terryww2
25 Feb 2019, 08:50

We were able to connect to Pepperstone again by setting the custom password for the FIX connection in cTrader. Which leads us to belive that with the update our custom password which we have setup Weeks ago, was overwritten.

@terryww2

Copyright © 2024 Spotware Systems Ltd. All rights reserved.
The services provided by Spotware Systems Ltd. are not available to citizens or residents of the USA. Neither is the information on our websites directed toward soliciting citizens or residents of the USA.