bml67
16 Apr 2025, 10:50

Update

I just updated to cTrader 5.3.62 on macOS — the bug is now resolved on this version 🎉

However, on the latest Windows version, the bug still persists, but I assume the Windows fix should be coming next. Fingers crossed 🤞

bml67
07 Apr 2025, 11:39

RE: RE: RE: RE: Multiple HTTP Requests Failing After First Request in cTrader 5.3.49

soskrr said: 

ctid8068054 said: 

soskrr said: 

bml67 said: 

Update:

I just tested the newly released cTrader version 5.3.60 today — unfortunately, the bug still persists.

The second HTTP request (regardless of where it’s placed — OnStart, OnTimer, etc.) still fails silently after the first one succeeds.

Any update yet? Did you get an estimated time?

Best Regards

 

Hello there, would anyone know of a workaround until cTrader bug fixed and released ? I am stuck on 5.2.5 

Hi, did you get a way to work around this? 

Hi,

I don’t, unfortunately.

If HTTP/S requests are mandatory for your bot, the only workaround for now is to use an older version of cTrader. Some brokers still offer their own version of the platform, and it’s usually one release behind — where the requests still work fine.

Otherwise, we’ll just have to wait for the bug fix release.

Let’s hope it’s coming soon!

bml67
23 Mar 2025, 17:46 ( Updated at: 24 Mar 2025, 06:56 )

Update:

I just tested the newly released cTrader version 5.3.60 today — unfortunately, the bug still persists.

The second HTTP request (regardless of where it’s placed — OnStart, OnTimer, etc.) still fails silently after the first one succeeds.

bml67
22 Mar 2025, 21:47 ( Updated at: 24 Mar 2025, 06:56 )

RE: Multiple HTTP Requests Failing After First Request in cTrader 5.3.49

soskrr said: 

Hi,

i am getting this error as well. It happened after the most recent update. did you get a way to fix it ?

Hi 👋

I contacted support and just received this response from them:

“Dear Trader,

Thank you for your patience in this matter. Please be advised that the issue at hand is indeed a bug and the team is actively working on it and we aim to release the fix in the next minor version update.

Thank you once again for your understanding.”

So it’s definitely a confirmed bug, and they’re already working on a fix. Hopefully it’ll be resolved in the next minor release. 🙌