Support Board
Date/Time: Mon, 03 Nov 2025 10:43:33 +0000
Can't login to remote chart server
View Count: 188
| [2025-10-09 19:45:58] |
| User909576 - Posts: 1 |
|
hi, i tried again, but same results with sierra. i wrote down what i have tried: I am experiencing connection issues when attempting to connect to your DTC (Data and Trading Communications) servers programmatically. After extensive testing and research, and i need your assistance. **Technical Implementation:** I have implemented a DTC client following your official documentation: DTC Protocol Implementation details: - Transport: TCP/TLS (as recommended in your documentation, not WebSocket) - Encoding: Binary with fixed-length strings (Type 0) - Protocol Version: 8 - Trade Mode: 2 (Simulated Trading) - Message Structure: 4-byte header (Size + Type) + message body - Size field: Includes the 4-byte header itself (as per documentation) - Implementation Reference: Based on DTC protocol specification and open-source implementations (e.g., python-ws-dtc-client by jason0598647) **Test Results:** ### Test 1: TCP/TLS with ENCODING_REQUEST 1. ✓ TCP connection establishes successfully 2. ✓ TLS/SSL handshake successful 3. ✓ ENCODING_REQUEST sent (Type=5, requesting Binary encoding) 4. ✗ **Server echoes ENCODING_REQUEST (Type=5) instead of sending ENCODING_RESPONSE (Type=6)** 5. ✗ **Server immediately closes connection** ### Test 2: TCP/TLS with Direct LOGON (skipping encoding negotiation) 1. ✓ TCP connection establishes successfully 2. ✓ TLS/SSL handshake successful 3. ✓ LOGON_REQUEST sent directly with Binary encoding 4. ✗ **Server closes connection immediately without any response** ### Test 3: WebSocket SSL Connection (Before discovering your documentation recommends TCP/TLS) 1. ✓ WebSocket connection establishes 2. ✓ Messages sent and received 3. ✗ Received LOGON_RESPONSE with Result=2 (Failed) 4. ✗ Garbage protocol version numbers in error messages ("720904", "1832976392") **Identified Issues:** ### Issue #1: Encoding Negotiation Bug I found a similar issue reported in your support board: SC as a DTC client connecting to SC/DTC server with encoding error The thread describes the exact same problem: - User received "Unexpected DTC Encoding: 1413743386" (garbage number) - We receive "C protocol version 720904/1832976392 is unsupported" (garbage numbers) - Root cause: Server's encoding configuration causes protocol parsing failures - Sierra Chart Engineering acknowledged this as a bug requiring a fix **Current symptoms matching the support board issue:** - Server echoes ENCODING_REQUEST instead of properly responding with ENCODING_RESPONSE - Garbage protocol version numbers when encoding mismatch occurs - Connection fails during encoding negotiation ### Issue #2: Credentials or Account Authorization Even when working around the encoding bug, the server: - Does not respond to LOGON_REQUEST at all - Immediately closes the connection - Suggests either invalid credentials or account lacks API access **Questions:** 1. **Encoding Bug Status**: Has the encoding negotiation bug reported in Thread #32406 been resolved? Our testing shows it still exists on ports 11085 for both futurestrading10 and futurestrading11. 2. **Credential 3. **Account Type**: Does this account type support programmatic DTC API access over TCP/TLS, or is it limited to Sierra Chart desktop client only? 4. **Account Activation**: Does the account need to be activated or configured specifically for DTC API access? 5. **Server Configuration**: What is the current encoding configuration for the DTC servers on port 11085? (Binary, JSON, or Google Protocol Buffers?) 6. **IP Whitelisting**: Are there any IP whitelisting or additional authentication requirements? 7. **Alternative Approach**: If the encoding negotiation is known to be problematic, what is the recommended way to establish a DTC connection? Should we assume a default encoding and skip ENCODING_REQUEST? I would greatly appreciate your assistance in: 1. Verifying the account credentials and authorization status 2. Confirming the current status of the encoding negotiation bug 3. Providing guidance on the correct connection procedure for your DTC servers 4. Any additional configuration needed for programmatic API access Thank you for your help. Please let me know if you need any additional information about our implementation, testing results, or log files. Date Time Of Last Edit: 2025-10-10 05:26:33
|
| [2025-10-11 17:08:07] |
| Sierra_Chart Engineering - Posts: 21285 |
|
That thread you linked to is 7.5 years old. Whatever the problem was there, it was resolved. It must have been some unusual scenario. Definitively there are no outstanding issues with the protocol negotiation and the encoding. This is just simply impossible. It will never even get looked at by us because we know there are no problems at all. You need to go through the documentation here: DTC Messages and Procedures: Encoding Request Sequence If the connection is being closed on the server, there is something faulty with the data you are sending to the server. That is definitive. The issue is on your side. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: