Home >> Support Board

Support Board

Date/Time: Tue, 14 May 2024 05:51:18 +0000

How to Post a Message for Support

connecting to CQG -> socket (4) | Encryption stream error encountered.

View Count: 1783

[2017-02-19 23:51:25] #1 [Go To First Post]
user8888 - Posts: 159
that message seems to be back. I'm in 1521. It was working well past friday. I've tried to connect today without success. Log excerpt: CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6925. \| 2017-02-19 23:48:14 socket (4) \| Creating socket. Using TLS 1.2. \| 2017-02-19 23:48:14 CQG FIX: Sending the Logon message. \| 2017-02-19 23:48:15 CQG FIX Trading \| Connected to trading server. \| 2017-02-19 23:48:15 CQG FIX Trading \| Connecting to market data server api.cqg.com \| 2017-02-19 23:48:15 CQG WebAPI \| Connecting to websocket server. \| 2017-02-19 23:48:15 CQG FIX \| FCM name: AMP \| 2017-02-19 23:48:15 CQG WebAPI websocket (5) \| Creating socket. Using TLS 1.2. \| 2017-02-19 23:48:15 CQG WebAPI websocket (5) \| Connect event error. Windows error code 10060: Se produjo un error durante el intento de conexión ya que la parte conectada no respondió adecuadamente tras un periodo de tiempo, o bien se produjo un error en la conexión establecida ya que el host conectado no ha podido responder. \| 2017-02-19 23:48:36 * CQG WebAPI websocket (5) \| Initiating close of socket by core. \| 2017-02-19 23:48:36 CQG WebAPI \| Websocket closed. \| 2017-02-19 23:48:36 CQG WebAPI websocket (5) \| Closed. \| 2017-02-19 23:48:36 CQG FIX Trading \| Websocket closed. \| 2017-02-19 23:48:36 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2017-02-19 23:48:36 To prevent further connection attempts, select 'File >> Disconnect'. \| 2017-02-19 23:48:36 CQG FIX: DisconnectFIX called. \| 2017-02-19 23:48:36 CQG FIX: Sending a Logout message. \| 2017-02-19 23:48:36 CQG FIX Trading \| Disconnected. \| 2017-02-19 23:48:36 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2017-02-19 23:48:36 socket (4) \| Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init \| 2017-02-19 23:48:37 socket (4) \| Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init \| 2017-02-19 23:48:37 socket (4) \| Initiating close of socket by core. \| 2017-02-19 23:48:37 CQG FIX: Socket closed without completing the logout sequence. \| 2017-02-19 23:48:37 socket (4) \| Shutdown started. Waiting for graceful close. \| 2017-02-19 23:48:37 CQG FIX: Disconnected. \| 2017-02-19 23:48:37 socket (4) \| Received socket Close event \| 2017-02-19 23:48:37 socket (4) \| Closed. \| 2017-02-19 23:48:37 File >> Disconnect selected. \| 2017-02-19 23:48:37 CQG FIX Trading \| Disconnected. \| 2017-02-19 23:48:37 Thank you.

[2017-02-20 00:01:47] #2 [Go To First Post]
User626121 - Posts: 82
Same here.

[2017-02-20 00:35:01] #3 [Go To First Post]
oicur12 - Posts: 17
Same issue here. Using 1518 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6925. \| 2017-02-20 00:25:12 socket (6) \| Creating socket. Using TLS 1.2. \| 2017-02-20 00:25:12 CQG FIX: Sending the Logon message. \| 2017-02-20 00:25:13 CQG FIX Trading \| Connected to trading server. \| 2017-02-20 00:25:13 CQG FIX Trading \| Connecting to market data server api.cqg.com \| 2017-02-20 00:25:13 CQG WebAPI \| Connecting to websocket server. \| 2017-02-20 00:25:13 CQG WebAPI websocket (7) \| Creating socket. Using TLS 1.2. \| 2017-02-20 00:25:13 CQG FIX \| FCM name: Rosenthal Collins \| 2017-02-20 00:25:13 CQG WebAPI websocket (7) \| Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. \| 2017-02-20 00:25:34 * CQG WebAPI websocket (7) \| Initiating close of socket by core. \| 2017-02-20 00:25:34 CQG WebAPI \| Websocket closed. \| 2017-02-20 00:25:34 CQG WebAPI websocket (7) \| Closed. \| 2017-02-20 00:25:34 CQG FIX Trading \| Websocket closed. \| 2017-02-20 00:25:34 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2017-02-20 00:25:34 To prevent further connection attempts, select 'File >> Disconnect'. \| 2017-02-20 00:25:34 CQG FIX: DisconnectFIX called. \| 2017-02-20 00:25:34 CQG FIX: Sending a Logout message. \| 2017-02-20 00:25:34 CQG FIX Trading \| Disconnected. \| 2017-02-20 00:25:34 socket (6) \| Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init \| 2017-02-20 00:25:34 socket (6) \| Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init \| 2017-02-20 00:25:34 socket (6) \| Initiating close of socket by core. \| 2017-02-20 00:25:34 CQG FIX: Socket closed without completing the logout sequence. \| 2017-02-20 00:25:34 socket (6) \| Shutdown started. Waiting for graceful close. \| 2017-02-20 00:25:34 CQG FIX: Disconnected. \| 2017-02-20 00:25:34 socket (6) \| Received socket Close event \| 2017-02-20 00:25:34 socket (6) \| Closed. \| 2017-02-20 00:25:34 Thank you. Date Time Of Last Edit: 2017-02-20 00:36:14

[2017-02-20 00:39:03] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
In response to post #1, we are checking on this. In response to post #2, post a copy of the Message Log following these instructions here: https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog 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

[2017-02-20 00:43:33] #5 [Go To First Post]
User626121 - Posts: 82
Reading Internal Order ID file. \| 2017-02-19 19:42:52 Reading Trade Orders file. \| 2017-02-19 19:42:52 Reading Trade Positions file. \| 2017-02-19 19:42:52 Software version: 1518 \| 2017-02-19 19:42:52 Uses New Spreadsheets \| 2017-02-19 19:42:52 Enabled for: Advanced Features. \| 2017-02-19 19:42:52 Enabled for: Sierra Chart Historical Data Service. \| 2017-02-19 19:42:52 Allow Support for Sierra Chart Data Feeds is enabled. \| 2017-02-19 19:42:52 Current selected Data/Trading service: CQG FIX Trading \| 2017-02-19 19:42:52 Chart Update Interval: 500 \| 2017-02-19 19:42:52 Data/Trade Service Settings automatically set. \| 2017-02-19 19:42:52 Time Zone: -05:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) \| 2017-02-19 19:42:52 2017-02-20 01:42:55 Local computer time \| 2017-02-19 19:42:52 2017-02-20 00:42:55 Local computer time in UTC \| 2017-02-19 19:42:52 2017-02-19 19:42:55 Local computer time in SC Time Zone \| 2017-02-19 19:42:52 2017-02-20 00:42:55 Server time in UTC \| 2017-02-19 19:42:52 Local computer UTC time and Server UTC time difference: 1 seconds. \| 2017-02-19 19:42:52 Program path: C:\SierraChart4\ \| 2017-02-19 19:42:52 Data Files path: C:\SierraChart4\Data\ \| 2017-02-19 19:42:52 OS Version Number: 6.2 \| 2017-02-19 19:42:52 Locale Setting: C \| 2017-02-19 19:42:52 Checking for new symbol settings for service code cqg \| 2017-02-19 19:42:52 HTTPS connection to www.sierrachart.com:443 (3) \| Creating socket. Using TLS 1.2. \| 2017-02-19 19:42:52 Symbol settings are up-to-date for cqg \| 2017-02-19 19:42:52 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6925. \| 2017-02-19 19:43:00 socket (4) \| Creating socket. Using TLS 1.2. \| 2017-02-19 19:43:00 HTTPS connection to www.sierrachart.com:443 (3) \| Socket gracefully closed by remote side. \| 2017-02-19 19:43:00 HTTPS connection to www.sierrachart.com:443 (3) \| Received socket Close event \| 2017-02-19 19:43:00 HTTPS connection to www.sierrachart.com:443 (3) \| Initiating close of socket by core. \| 2017-02-19 19:43:00 HTTPS connection to www.sierrachart.com:443 (3) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2017-02-19 19:43:00 HTTPS connection to www.sierrachart.com:443 (3) \| Closed. \| 2017-02-19 19:43:00 CQG FIX: Sending the Logon message. \| 2017-02-19 19:43:00 CQG FIX Trading \| Connected to trading server. \| 2017-02-19 19:43:01 CQG FIX Trading \| Connecting to market data server api.cqg.com \| 2017-02-19 19:43:01 CQG WebAPI \| Connecting to websocket server. \| 2017-02-19 19:43:01 CQG WebAPI websocket (5) \| Creating socket. Using TLS 1.2. \| 2017-02-19 19:43:01 CQG FIX \| FCM name: AMP \| 2017-02-19 19:43:01 CQG WebAPI websocket (5) \| Connect event error. Windows error code 10060: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. \| 2017-02-19 19:43:22 * CQG WebAPI websocket (5) \| Initiating close of socket by core. \| 2017-02-19 19:43:22 CQG WebAPI \| Websocket closed. \| 2017-02-19 19:43:22 CQG WebAPI websocket (5) \| Closed. \| 2017-02-19 19:43:22 CQG FIX Trading \| Websocket closed. \| 2017-02-19 19:43:22 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2017-02-19 19:43:22 To prevent further connection attempts, select 'File >> Disconnect'. \| 2017-02-19 19:43:22 CQG FIX: DisconnectFIX called. \| 2017-02-19 19:43:22 CQG FIX: Sending a Logout message. \| 2017-02-19 19:43:22 CQG FIX Trading \| Disconnected. \| 2017-02-19 19:43:22 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2017-02-19 19:43:22 socket (4) \| Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init \| 2017-02-19 19:43:22 socket (4) \| Encryption stream error encountered. error:140E0197:SSL routines:SSL_shutdown:shutdown while in init \| 2017-02-19 19:43:22 socket (4) \| Initiating close of socket by core. \| 2017-02-19 19:43:22 CQG FIX: Socket closed without completing the logout sequence. \| 2017-02-19 19:43:22 socket (4) \| Shutdown started. Waiting for graceful close. \| 2017-02-19 19:43:22 CQG FIX: Disconnected. \| 2017-02-19 19:43:22 socket (4) \| Received socket Close event \| 2017-02-19 19:43:23 socket (4) \| Closed. \| 2017-02-19 19:43:23

[2017-02-20 00:52:35] #6 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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

[2017-02-20 08:32:22] #7 [Go To First Post]
User60579 - Posts: 41
Same problem here, trying to connect to CQG from sweden...

[2017-02-20 09:31:26] #8 [Go To First Post]
User885971 - Posts: 4
I just tested connecting using a US based VPN, and everything runs fine on that. Connecting without VPN from Europe doesn't work.

[2017-02-20 09:42:52] #9 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Thank you for the information in post #8. This confirms what we thought. 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 Date Time Of Last Edit: 2017-02-20 09:43:15

To post a message in this thread, you need to log in with your Sierra Chart account: