paolob
06 Dec 2023, 00:39

RE: RE: Server Error when trying to get new access token

LogicFX said: 

michael00 said: 

Hello, I have the same situation ( server error ), I tried with different browsers, and also I tried in another machine on my VPS but received the same error.

Good news, it seems to work now

Confirmed working! Also, on the id.ctrader.com site, RoboForex is no longer listed as one of my broker/account

Thanks!

paolob
28 Nov 2023, 07:23 ( Updated at: 21 Dec 2023, 09:23 )

RE: Server Error when trying to get new access token

LogicFX said: 

Support team may be able to reproduce it, just trying to add an account in myfxbook, going to porfolio → add account

The generated URI is: 

https://connect.spotware.com/oauth/v2/auth?access_type=online&approval_prompt=auto&client_id=3_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&redirect_uri=https://www.myfxbook.com/ctrader_auth&response_type=code&scope=accounts

(replaced the real id with xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)

That generates the same error 500 you showed in the first post

I was speaking to technical support on telegram, they added logs to my account and I triggered the 500 Server Error on my side

Here is a snippet of my conversation:

This conversation is still in progress, but I had an old account on RoboForex, and since they are no longer a cTrader broker, my Spotware account still lists RoboForex as part of all my accounts. So it seems the developers are saying to tech support that “He told me that the response from our server is of type of unexisting broker.” refers to RoboForex.

Maybe you have the same situation as I have, we have orphaned data on the Spotware side which is causing the 500 Server Error to occur.

I will keep everyone posted.

paolob
26 Nov 2023, 15:09 ( Updated at: 21 Dec 2023, 09:23 )

RE: RE: Reply to: Server Error when trying to get new access token

paolob said: 

PanagiotisCharalampous said: 

Hi there,

Thanks for reporting this issue. Our team is investigating.

Best regards,

Panagiotis

Hello @PanagiotisCharalampous

I was speaking to Open API Support via Telegram, he requested this: 

I have initiated these attempts so that the developers/support can examine the logs:

3:01 PM 26NOV2023 UTC -- 6 attempts to get a “Trading” scope Access Token, all returned with 500 Server Error

3:02PM 26NOV2023 UTC -- 6 attempts to get an “Accounts” scope Access Token, all returned with 500 Server Error

Thank you again for helping me out with my issue.

I forgot to mention, i also registered a new cTrader Application via openapi.ctrader.com, the application has been activated, but generating Access Tokens for both “Trading” and “Accounts” scopes produced the same 500 Server Error

paolob
26 Nov 2023, 15:06 ( Updated at: 21 Dec 2023, 09:23 )

RE: Reply to: Server Error when trying to get new access token

PanagiotisCharalampous said: 

Hi there,

Thanks for reporting this issue. Our team is investigating.

Best regards,

Panagiotis

Hello @PanagiotisCharalampous

I was speaking to Open API Support via Telegram, he requested this: 

I have initiated these attempts so that the developers/support can examine the logs:

3:01 PM 26NOV2023 UTC -- 6 attempts to get a “Trading” scope Access Token, all returned with 500 Server Error

3:02PM 26NOV2023 UTC -- 6 attempts to get an “Accounts” scope Access Token, all returned with 500 Server Error

Thank you again for helping me out with my issue.

paolob
21 Nov 2023, 14:09 ( Updated at: 21 Dec 2023, 09:23 )

RE: Reply to: Server Error when trying to get new access token

PanagiotisCharalampous said: 

Hi there,

Thanks for reporting this issue. Our team is investigating.

Best regards,

Panagiotis

Thank you! i contacted “Open API Support” on Telegram earlier, I have given screenshots and information there.

The strange thing is that my colleague was able to generate a new Access Token on his account, but on mine, I tried different browsers (the first time to visit the Open API website on these browsers) and I got the same exact 500 Server Error.

This applies to both “Accounts” and “Trading” scopes when I click the “Get Token” button.

I have noticed on Google Chrome, that there were JavaScript errors related to “Counter hint not found.”, I am unsure if this is related to the issue (this Javascript error also occurs on Microsoft Edge and Firefox.

All of my browsers are fully updated and are the latest versions.

Thank you for investigating, I really appreciate it

paolob
24 Sep 2022, 03:01

RE:

I eventually figured it out, when the cTrader.OpenAPI.NET library initializes the OpenClient class, the host parameter is typically retrieved via the ApiInfo.GetHost() method, which returns "demo.ctraderapi.com" or "live.ctraderapi.com".

However, when I was reading the documentation I found the article about Proxies/Endpoints (https://help.ctrader.com/open-api/proxies-endpoints/) and it outlines several regional proxy servers to use, such as "demo-sg.ctraderapi.com" etc, so I tried this out and just hardcoded the host parameter to the OpenClient ctor and it worked!

I was able to connect and issue ProtoOA* requests to the OpenAPI server without any problems.

paolobrionesph@gmail.com said:

Hello,

This issue started happening this morning (Manila, PH time).

The initial call to ProtoOAApplicationAuthReq/ProtoOAApplicationAuthRes was completed successfully and my application was able to authenticate with my Client ID/Secret.

The secondary call to ProtoOAAccountAuthReq/ProtoOAAccountAuthRes hangs and never returns any value via the Subscribe() response handler, no errors were also reported. it just hangs indefinitely.

This issue also happens to both Demo Spotware accounts, and Live ICM/Pepperstone accounts.

I remember this happening in the past, but after a few hours everything worked again properly.

 

I am currently running the code in C#, VS2022 (fully patched), ASPNETCORE 6, Dotnet6, Windows 11 (fully patched), no changes to the existing code and the same code worked yesterday without any issues. Using the latest version of cTrader.OpenAPI.NET v1.4.4 from nuget

 

Looking forward to a resolution to the problem :(

Sincerely,

Paolo