What are cTrader Cloud limitations for HTTP and WebSocket connections?

What this means in practice

cTrader Cloud runs cBots in Linux. Official documentation says HTTP requests are not sent in Cloud and WebSocketClient works only through port 25345; Windows-only dependencies also fail. This page is specifically about “What are cTrader Cloud limitations for HTTP and WebSocket connections?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — HTTP works local not Cloud

Inspect the mechanism named by “Scenario A — HTTP works local not Cloud” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — HTTP works local not Cloud on question 47, use that evidence specifically to answer “What are cTrader Cloud limitations for HTTP and WebSocket connections?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Wrong WebSocket port

Inspect the mechanism named by “Scenario B — Wrong WebSocket port” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Wrong WebSocket port on question 47, use that evidence specifically to answer “What are cTrader Cloud limitations for HTTP and WebSocket connections?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Windows dependency

Inspect the mechanism named by “Scenario C — Windows dependency” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Windows dependency on question 47, use that evidence specifically to answer “What are cTrader Cloud limitations for HTTP and WebSocket connections?”; keep it separate from the evidence for the other scenarios on this page.

What to check

• target connector/account identity
• exact broker symbol
• normalized order parameters
• cTrader response and final position/order state

Practical rule

For “What are cTrader Cloud limitations for HTTP and WebSocket connections?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.