BUG: Persistent "Login Failed" - Console v5.6.8

[celestynuno-cmyk]

Hello,

Regarding console v5.6.8:

I noticed a recurring issue where the connection to the trading account is lost and fails to reconnect automatically.
This is occurring daily and is severely impacting the reliability of algorithmic trading.

Issue Details:

• Context: The cBot is already running when the disconnection occurs.
• Behavior: Internet connectivity is verified and stable (SSH session remains active during failures). However, after disconnecting, the console enters a "Login failed" loop. Credentials are valid, but the console seems to lose its authentication state/handshake ability.
• Frequency: Daily / multiple times a day.
• Workaround: Only a full container restart restores the connection.

For your reference, I have attached the Docker logs highlighting the timestamps and subsequent login rejections.
Please treat this fix as high priority to ensure the Console is a viable solution for algo trading.

Thank you.

[amusleh-spotware-com]

Hi,

We are aware of this issue, can you please use image version ctrader-console:5.7.1-alpha with full verbose logging enabled by passing logging env variables when you run:

-e ctrader-algo-logs='1' -e ctrader-logs='1' -e ctrader-test-tools='1'

When issue occurred again post full log of your container and we will check, thanks.

[celestynuno-cmyk]

Hi @amusleh-spotware-com ,

Thanks for your reply.

The cBot fails to start when launched via ctrader-console:5.7.1-alpha
It gets stuck at Starting cBot... as shown below.

[amusleh-spotware-com]

Hi @celestynuno-cmyk ,

Please try image ctrader-console:5.7.2-alpha, and let me know if you faced any issue.

[celestynuno-cmyk]

@amusleh-spotware-com

Thanks for the prompt reply.
It is running now!! I will keep you informed.

[celestynuno-cmyk]

Hi @amusleh-spotware-com ,

Connection has been lost again, after a few hours. See below.
Should you need any further info please let me know.

[amusleh-spotware-com]

Hi @celestynuno-cmyk,

As I said on my previous comment, please run the new image with logging variables that will enable full verbose logging and when this issue occurred again post your container full log here, that will help us.

We need your container full console log from start to end.

[celestynuno-cmyk]

Hi @amusleh-spotware-com ,

The console was running with the extra arguments/variables you mentioned.
Below is the full run command I used. Let me know if this is correct.

[amusleh-spotware-com]

Hi @amusleh-spotware-com ,

The console was running with the extra arguments/variables you mentioned.
Below is the full run command I used. Let me know if this is correct.

Then can you please attach your container full console log here?

[celestynuno-cmyk]

Hi @amusleh-spotware-com ,

Log has been deleted by mistake (container removed) and I need to run the console:5.7.2-alpha console again.

However, I noticed from console:5.6.8 logs that "Login failed" is being printed within microseconds. This suggests a CPU-bound "tight loop" where the console is effectively DDOS-ing itself locally, meaning nothing is reaching or being received from the server. See the attached screenshot.

If this is still the case with console:5.7.2-alpha, please fix it first (e.g. 5min await), so that I am able to provide the full log, otherwise I won't even be able to open the file.

FYI, I have an existing log file sized 16.4 GB (130 million lines - an absurdity) as a result of this behavior.

I also noticed that the "Login failed" issue is cBot agnostic, since it already failed using a cBot that only prints a simple message OnTimer() every 5 min. This means you should be able to easily reproduce this issue on your end as well.