Home >> Support Board

Support Board

Date/Time: Tue, 23 Apr 2024 23:07:08 +0000

How to Post a Message for Support

CQG agreement LINUX

View Count: 1506

[2019-02-22 09:50:20] #1 [Go To First Post]
User967010 - Posts: 7
Hello, i have connection problem to CQG. Version 1847 connect without any problems but latest version 1875 dont connect to CQG. I run Sierra Chart under linux Fedora 29 Wine 4. 'In order to be able to connect to CQG, CQG is requiring you to complete the end user license agreement. If you are running version 1872 or higher, if you have not already signed this agreement, the agreement will open in your web browser when there is a connection attempt to CQG.' No agreement will popout.

[2019-02-22 09:52:46] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Reconnect to the data feed: File Menu: Procedure to Reconnect to the Data and Trade Servers After about 30 seconds, provide a copy of the Message Log following these instructions: 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

[2019-02-22 10:52:27] #3 [Go To First Post]
AlexPereira - Posts: 197
If i may ask without interfering, user User967010, can you try connecting without loading any instruments ( without loading any chartbooks and no symbols in intraday file update list ) ? versions until 1847, if i am not mistaken, connect well in linux, but afterwards, there are issues connecting with lots of instruments in the background. ( this was talked and confirmed on the linux topic on this forum )

[2019-02-27 07:52:01] #4 [Go To First Post]
User967010 - Posts: 7
AlexPereira: i installed 1875 and it connected without any problems to CQG (without any chartbooks) but with my chartbook im loosing connection nonstop. :(

[2019-02-27 13:53:04] #5 [Go To First Post]
User75096 - Posts: 48
here the same i tried everything , now im back to 47 ,connction is fine but chartbook with more than two charts it reconnect

[2019-02-28 08:44:34] #6 [Go To First Post]
User967010 - Posts: 7
I solved it by duplicate all my charts (13) to a new chartbook and problems with reconnections are gone ..1875 now.. ;)

[2023-01-11 14:20:14] #7 [Go To First Post]
User388924 - Posts: 1
I have the same problem connection to CQG. The workaround connection without an open chartbook does not work in my case. How can I sign the End User License Agreement? The link does not open and I don't know where to find the agreement. Attached I sent you the message log. Many thanks for your support! Software version: 2458 64-bit \| 2023-01-11 09:13:32.745 Primary Thread ID: 10244 \| 2023-01-11 09:13:32.745 Usage end date: 2023-01-18 \| 2023-01-11 09:13:32.745 Enabled for: Advanced Features 2. \| 2023-01-11 09:13:32.745 Enabled for: Sierra Chart Historical Data Service. \| 2023-01-11 09:13:32.745 Enabled for: Denali Real-Time Exchange Data Feed. \| 2023-01-11 09:13:32.745 Enabled for: Delayed Denali Exchange Data Feed. \| 2023-01-11 09:13:32.745 Enabled for exchange2: fairx_exchange.data \| 2023-01-11 09:13:32.745 Allow Support for Sierra Chart Data Feeds is enabled. \| 2023-01-11 09:13:32.745 Current selected Data/Trading service: CQG WebAPI \| 2023-01-11 09:13:32.745 Custom symbol settings values: enabled \| 2023-01-11 09:13:32.745 Chart Update Interval: 500 \| 2023-01-11 09:13:32.745 Intraday Data Storage Time Unit: 1 \| 2023-01-11 09:13:32.745 Time Zone: -05:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) \| 2023-01-11 09:13:32.745 2023-01-11 14:13:32 Local computer time in UTC \| 2023-01-11 09:13:32.745 2023-01-11 09:13:32 Local computer time in SC Time Zone \| 2023-01-11 09:13:32.745 2023-01-11 14:04:24 Server time in UTC \| 2023-01-11 09:13:32.745 Local computer UTC time and Server UTC time difference: 1 seconds. \| 2023-01-11 09:13:32.745 Program path: C:\SierraChart\ \| 2023-01-11 09:13:32.745 Data Files path: C:\SierraChart\Data\ \| 2023-01-11 09:13:32.745 OS Version Number: 10.0 \| 2023-01-11 09:13:32.745 Locale Setting: C \| 2023-01-11 09:13:32.745 DLLs: UserContributedStudies_64.dll \| 2023-01-11 09:13:32.746 Allowed protected custom studies: \| 2023-01-11 09:13:32.746 Crash reporter started: true \| 2023-01-11 09:13:32.746 CQG WebAPI \| Connecting to server api.cqg.com \| 2023-01-11 09:14:11.882 CQG WebSocket \| Connecting to WebSocket server api.cqg.com:443 \| 2023-01-11 09:14:11.882 CQG WebSocket socket (1) \| Creating socket. Using TLS 1.2. \| 2023-01-11 09:14:12.099 CQG WebSocket socket (1) \| New receive buffer size: 5242880 \| 2023-01-11 09:14:12.099 CQG WebSocket socket (1) \| Connecting to IP: 195.166.124.165. \| 2023-01-11 09:14:12.099 CQG WebSocket \| Opening WebSocket. \| 2023-01-11 09:14:12.168 CQG WebSocket \| Sending WebSocket handshake. \| 2023-01-11 09:14:12.168 CQG WebSocket \| Server header \| HTTP/1.1 101 Switching Protocols \| 2023-01-11 09:14:12.371 CQG WebSocket \| Server header \| Connection: upgrade \| 2023-01-11 09:14:12.371 CQG WebSocket \| Server header \| Sec-WebSocket-Accept: 9yzM640QnitBnWWp1kn4L7lme4Y= \| 2023-01-11 09:14:12.371 CQG WebSocket \| Server header \| Server: WebSocket++/0.7.0 \| 2023-01-11 09:14:12.371 CQG WebSocket \| Server header \| Upgrade: websocket \| 2023-01-11 09:14:12.371 CQG WebSocket \| Server header \| \| 2023-01-11 09:14:12.371 CQG WebSocket \| Web socket state is now open. \| 2023-01-11 09:14:12.371 CQG WebAPI \| WebSocket connected. \| 2023-01-11 09:14:12.371 CQG WebAPI \| Sending market data logon message. \| 2023-01-11 09:14:12.371 CQG WebAPI \| Logon unsuccessful. Server message: You must accept the terms of the End User License Agreement. Visit: https://my.cqg.com/token/BWIkasFIR7WNObYCFgO7fA . \| 2023-01-11 09:14:12.634 CQG WebSocket socket (1) \| CloseSocket call. \| 2023-01-11 09:14:12.637 CQG WebAPI \| Disconnected. \| 2023-01-11 09:14:12.637 CQG WebAPI \| Not reconnecting due to connection error condition. \| 2023-01-11 09:14:12.637 CQG WebSocket \| WebSocket closed. \| 2023-01-11 09:14:12.637 CQG WebAPI \| WebSocket closed. \| 2023-01-11 09:14:12.637 CQG WebSocket socket (1) \| Write in progress. Shutdown being delayed. PendingSize=0 \| 2023-01-11 09:14:12.637 CQG WebSocket socket (1) \| Write has completed. Shutdown being performed. \| 2023-01-11 09:14:12.700 CQG WebSocket socket (1) \| Shutdown started. Waiting for graceful close. \| 2023-01-11 09:14:12.700

[2023-01-11 16:03:26] #8 [Go To First Post]
Sierra_Chart Engineering - Posts: 14064
Contact your broker for any help with signing the CQG agreement. Clearly you cannot connect without doing that. 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 Date Time Of Last Edit: 2023-01-11 16:03:35

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