Support Board
Date/Time: Sun, 12 Jan 2025 15:43:20 +0000
Post From: connecting to CQG -> socket (4) | Encryption stream error encountered.
| [2017-02-20 00:52:35] |
| |
|
One thing that is common between both of you is that you are both in Europe. We have no problem ourselves with the connection. This is the log: CQG WebAPI | Connecting to server api.cqg.com | 2017-02-19 19:39:50
CQG WebAPI | Connecting to websocket server. | 2017-02-19 19:39:50 CQG WebAPI websocket (26) | Creating socket. Using TLS 1.2. | 2017-02-19 19:39:50 CQG WebAPI websocket (26) | Receive buffer size: 262144 | 2017-02-19 19:39:50 CQG WebAPI websocket (26) | Send buffer size: 0 | 2017-02-19 19:39:50 CQG WebAPI | Opening websocket. | 2017-02-19 19:39:50 CQG WebAPI | Sending websocket handshake. | 2017-02-19 19:39:50 CQG WebAPI websocket (26) | OwnerReceiveProcessingBuffer size = 156 | 2017-02-19 19:39:51 CQG WebAPI | Received websocket handshake acknowledgment. | 2017-02-19 19:39:51 CQG WebAPI | Web socket state is now open. | 2017-02-19 19:39:51 CQG WebAPI | Websocket connected. | 2017-02-19 19:39:51 CQG WebAPI | Sending market data logon message. | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | Bytes removed from receive buffer = 156 | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | OwnerReceiveProcessingBuffer size = 74 | 2017-02-19 19:39:51 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2017-02-19 19:39:51 * CQG WebAPI websocket (26) | Adding bytes from final send buffer from buffered socket: 8 | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | Initiating close of socket by core. | 2017-02-19 19:39:51 CQG WebAPI | Websocket closed. | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | Sending bytes from final send buffer: 8 | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | Write in progress. Shutdown being delayed. | 2017-02-19 19:39:51 CQG WebAPI | Websocket closed. | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | Write has completed. Shutdown being performed. | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | Shutdown started. Waiting for graceful close. | 2017-02-19 19:39:51 CQG WebAPI | Disconnected. | 2017-02-19 19:39:51 CQG WebAPI websocket (26) | Socket gracefully closed by remote side. | 2017-02-19 19:39:54 CQG WebAPI websocket (26) | Closed. | 2017-02-19 19:39:54 This log is much more detailed but there is no trouble at all with the connection. What is clear from your Message Logs is that there simply is trouble even initiating the connection to the CQG web socket server. We are contacting CQG about this now. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |