IBKR TWS connector issues

[SkyrockIntelli]

Bug Report

2025-08-11T12:30:11.130438770Z [WARN] volcarry-001.InteractiveBrokersClient-001: Failed to receive server version information, retries remaining: 4
2025-08-11T12:30:13.133094561Z [WARN] volcarry-001.InteractiveBrokersClient-001: Failed to receive server version information, retries remaining: 3
2025-08-11T12:30:15.135712666Z [WARN] volcarry-001.InteractiveBrokersClient-001: Failed to receive server version information, retries remaining: 2
2025-08-11T12:30:17.138417231Z [WARN] volcarry-001.InteractiveBrokersClient-001: Failed to receive server version information, retries remaining: 1
2025-08-11T12:30:19.140980542Z [WARN] volcarry-001.InteractiveBrokersClient-001: Failed to receive server version information, retries remaining: 0
2025-08-11T12:30:20.142163801Z [ERROR] volcarry-001.InteractiveBrokersClient-001: Connection failed
2025-08-11T12:30:20.142691888Z [ERROR] volcarry-001.InteractiveBrokersClient-001: Couldn't connect to TWS. Confirm that "Enable ActiveX and Socket EClients" is enabled and connection port is the same as "Socket Port" on the TWS "Edit->Global Configuration...->API->Settings" menu. Live Trading ports: TWS: 7496; IB Gateway: 4001. Simulated Trading ports for new installations of version 954.1 or newer: TWS: 7497; IB Ga
teway: 4002 (code: 502, req_id=-1)
2025-08-11T12:30:20.142711956Z [ERROR] volcarry-001.InteractiveBrokersClient-001: Not connected (code: 504, req_id=-1)
2025-08-11T12:30:35.144007901Z [ERROR] volcarry-001.InteractiveBrokersClient-001: Client failed to initialize; connection timeout

Use this template only for issues that fit the Bug definition.

Term	Definition
Bug	Behavior that contradicts the platform’s documented or intended design as per code, docs, or specs. (i.e., the implementation is incorrect.)
Expectation mismatch	Behavior that follows the platform’s documented or intended design but differs from what you expected. (i.e., the design/spec might be the problem.)
Enhancement request	A request for new functionality or behavior that is not implied by existing design. (i.e., “It would be great if the platform could…”)

Note:

• Submitting this issue automatically applies the bug label.
• bug-labeled issues are triaged with higher priority because they require corrective implementation work.
• Expectation mismatches and design-level concerns should be opened as Discussions, or RFCs instead, where they can be validated and discussed to consensus before any work is scheduled.
• The absence of a feature is typically not an expectation mismatch, and should be filed as an enhancement request.

Confirmation

Before opening a bug report, please confirm:

• I’ve re-read the relevant sections of the documentation.
• I’ve searched existing issues and discussions to avoid duplicates.
• I’ve reviewed or skimmed the source code (or examples) to confirm the behavior is not by design.
• I’ve tested this issue using a recent development wheel (dev develop or a nightly) and can still reproduce it.

Checking a recent development wheel can save time because the issue may already have been fixed.
You can install a development wheel by running:

pip install -U nautilus_trader --pre --index-url https://packages.nautechsystems.io/simple

See the development-wheels section for more details.

Expected Behavior

Add here...

Actual Behavior

Add here...

Steps to Reproduce the Problem

Code Snippets or Logs

Specifications

• OS platform:
• Python version:
• nautilus_trader version:

[DracheShiki]

#2726
check if your language-decoding is included.
line 89: for enc in ["utf-8", "gbk", "latin-1", "cp1252"]: