honfaikan5
17 Oct 2024, 21:09

RE: INVALID_REQUEST on PROTO_OA_GET_TRENDBARS_REQ

Thank you for the reply Panagiotis! It turned out there's a race condition. The application got authenticated but the trendbar request was sent before the confirmation is returned. That's why the other requests were successful. 😅 Thank you again for the support!

PanagiotisCharalampous said: 

Hi there,

Did you check the obvious? That the account id is correct?

Best regards,

Panagiotis

honfaikan5
13 Nov 2023, 13:39

Thank you so much for the help! My issue got resolved in Telegram.

honfaikan5
10 Nov 2023, 18:24 ( Updated at: 11 Nov 2023, 07:05 )

Thank you Panagiotis. I got some ideas from the Telegram space, but now I can't seem to connect to try out those ideas. It seems like 5035 works but the SSL certificate is now invalid, and 5036 doesn't respond at all. I'm trying to use Websocket/JSON option (port 5036). I've tried the following on both my local machine and a Linode machine external to my network. Any idea what else I could try?

$ websocat -v wss://demo1.p.ctrader.com:5035
[INFO  websocat::lints] Auto-inserting the line mode
[INFO  websocat::stdio_threaded_peer] get_stdio_peer (threaded)
[INFO  websocat::ws_client_peer] get_ws_client_peer
websocat: WebSocketError: WebSocket SSL error: The certificate was not trusted.
websocat: error running

$ websocat -v wss://demo1.p.ctrader.com:5036
[INFO  websocat::lints] Auto-inserting the line mode
[INFO  websocat::stdio_threaded_peer] get_stdio_peer (threaded)
[INFO  websocat::ws_client_peer] get_ws_client_peer
websocat: WebSocketError: I/O failure
websocat: error running

Thank you for any insights!