DTC Protocol Discussion Forum
- DTC Protocol Discussion Forum |
- Search Board |
- Control Panel |
- View My Posts / Threads |
- Direct Messages
Date/Time: Fri, 29 Nov 2024 12:52:05 +0000
[Locked] - Sierra Chart can't read the incoming decrypted data
View Count: 5015
| [2022-03-06 11:06:26] |
| User667066 - Posts: 3 |
|
Hi, I tried to use the DTC Protocol for Sierra Chart. I can create the connection, but when I make a simple MARKET_DATA_REQUEST like this: b'{"Type": 101, "RequestAction": 1, "SymbolID": 1, "Symbol": "ETHUSDT_PERP_BINANCE", "Exchange": "BINANCE"}\x00'
I get this error in the Message Log: Encryption stream error encountered when processing received data. Failed to read incoming decrypted data from the incoming binary I/O stream. error:1408F10B:SSL routines:ssl3_gete_record:wrong version number
Full Message Log: DTC Protocol server | Incoming connection from 127.0.0.1. | 2022-03-06 11:02:42.501 DTC client #32. 127.0.0.1 | Waiting for TLS negotiation from client. | 2022-03-06 11:02:42.504 DTC client #32. 127.0.0.1 (2) | Creating socket. Using TLS 1.2. | 2022-03-06 11:02:42.504 DTC client #32. 127.0.0.1 (2) | New receive buffer size: 262144 | 2022-03-06 11:02:42.504 DTC client #32. 127.0.0.1 (2) | Allocated send buffers: 32 of 131072 bytes. | 2022-03-06 11:02:42.505 DTC client #32. 127.0.0.1 (2) | Encryption stream error encountered when processing received data. Failed to read incoming decrypted data from the incoming binary I/O stream. error:1408F10B:SSL routines:ssl3_get_record:wrong version number | 2022-03-06 11:02:42.505 DTC client #32. 127.0.0.1 (2) | CloseSocket call. | 2022-03-06 11:02:42.505 DTC client #32. 127.0.0.1 (2) | Shutdown started. Waiting for graceful close. | 2022-03-06 11:02:42.505 Deleting individual DTC server: DTC client #32. 127.0.0.1 | 2022-03-06 11:02:42.505 DTC server: DTC client #32. 127.0.0.1 successfully deleted. | 2022-03-06 11:02:42.506 |
| [2022-03-17 17:27:33] |
| |
|
In our experience this indicates, a wrong TLS version being used on the other side.
|
To post a message in this thread, you need to log in with your Sierra Chart account: