Support Board
Date/Time: Sun, 02 Feb 2025 13:06:08 +0000
Bitmex trade service connection issues
View Count: 1186
| [2019-09-08 16:56:34] |
| greyscape - Posts: 4 |
|
I haven't been able to connect my charts to bitmex api for the past week and I've attempted all of the self troubleshooting options on the sierra website. This is the error message that prints on a loop in my log. Reading Internal Order ID file. | 2019-09-08 16:33:16.736 Reading Trade Orders file. | 2019-09-08 16:33:16.841 Reading Trade Positions file. | 2019-09-08 16:33:16.842 Reading Account Balance file. | 2019-09-08 16:33:16.843 UDPListener (1500). Port 22904 | Listening on UDP port 22904. | 2019-09-08 16:33:16.867 Software version: 1986 32-bit | 2019-09-08 16:33:16.868 Usage end date: 2019-09-26 | 2019-09-08 16:33:16.868 Enabled for: Advanced Features 2. | 2019-09-08 16:33:16.868 Enabled for: Sierra Chart Historical Data Service. | 2019-09-08 16:33:16.868 Allow Support for Sierra Chart Data Feeds is enabled. | 2019-09-08 16:33:16.868 Current selected Data/Trading service: BitMEX Trading Direct | 2019-09-08 16:33:16.868 Custom symbol settings values: enabled | 2019-09-08 16:33:16.868 Chart Update Interval: 500 | 2019-09-08 16:33:16.868 Intraday Data Storage Time Unit: 0 | 2019-09-08 16:33:16.868 Time Zone: +00:00:00 (UTC+00) | 2019-09-08 16:33:16.868 2019-09-08 09:33:16 Local computer time | 2019-09-08 16:33:16.868 2019-09-08 16:33:16 Local computer time in UTC | 2019-09-08 16:33:16.868 2019-09-08 16:33:16 Local computer time in SC Time Zone | 2019-09-08 16:33:16.868 2019-09-08 16:33:17 Server time in UTC | 2019-09-08 16:33:16.868 Local computer UTC time and Server UTC time difference: 1 seconds. | 2019-09-08 16:33:16.868 Program path: C:\SierraChart\ | 2019-09-08 16:33:16.868 Data Files path: C:\SierraChart\Data\ | 2019-09-08 16:33:16.868 OS Version Number: 10.0 | 2019-09-08 16:33:16.868 Locale Setting: C | 2019-09-08 16:33:16.868 DLLs: UserContributedStudies.dll, UserContributedStudies_64.dll | 2019-09-08 16:33:16.869 Created the DTC Protocol server. | 2019-09-08 16:33:16.869 DTC Protocol Server listening on port 11099. | 2019-09-08 16:33:16.870 Created the DTC Protocol historical data server. | 2019-09-08 16:33:16.870 HD Server Manager | Listening on port 11098 | 2019-09-08 16:33:16.871 Checking for new symbol settings. Requested symbol settings MD5 for service code bitmex.exchange.trading. Request ID: 1. | 2019-09-08 16:33:16.871 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Shutdown started. Waiting for graceful close. | 2019-09-08 16:33:16.888 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:17.089 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Closed. | 2019-09-08 16:33:17.089 Received 5 login tokens. | 2019-09-08 16:33:17.624 Symbol settings MD5 received. Request ID: 1. | 2019-09-08 16:33:17.779 Requested symbol settings for service code bitmex.exchange.trading. Request ID: 2. | 2019-09-08 16:33:17.779 Symbol settings received. Request ID: 2. | 2019-09-08 16:33:19.241 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-09-08 16:33:22.814 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-09-08 16:33:22.814 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-09-08 16:33:23.052 BitMEX Trading Direct socket (1) | Connecting to IP: 54.229.111.9. | 2019-09-08 16:33:23.052 BitMEX Trading Direct | Opening WebSocket. | 2019-09-08 16:33:23.227 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-09-08 16:33:23.227 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | Date: Sun, 08 Sep 2019 16:33:25 GMT | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | Connection: upgrade | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | Set-Cookie: AWSALB=Vl205iZyaat3BG74OA9XZmMP6ujhRMlmjHUrwIsKHSKS7KhzGdKlm1BWMBRVTgDrAtM4wSc+VHnOXkOmd+zcI2KXbc9IqKd1kFoBDBGw1g/RnlYHheYKLWKmwtep; Expires=Sun, 15 Sep 2019 16:33:25 GMT; Path=/ | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | Upgrade: websocket | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | Sec-WebSocket-Accept: Qq/kgnhQbjQVPgtnYfC2sTPWTW0= | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | Sec-WebSocket-Version: 13 | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | WebSocket-Server: uWebSockets | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | Strict-Transport-Security: max-age=31536000; includeSubDomains | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Server header | | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:33:23.830 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:27.241 Connection to the external service has been lost. | 2019-09-08 16:33:27.241 BitMEX Trading Direct socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-09-08 16:33:27.241 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:33:27.254 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-09-08 16:33:27.254 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-09-08 16:33:30.254 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-09-08 16:33:30.254 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-09-08 16:33:30.255 BitMEX Trading Direct socket (1) | Connecting to IP: 54.229.111.9. | 2019-09-08 16:33:30.255 BitMEX Trading Direct | Opening WebSocket. | 2019-09-08 16:33:30.452 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-09-08 16:33:30.452 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | Date: Sun, 08 Sep 2019 16:33:32 GMT | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | Connection: upgrade | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | Set-Cookie: AWSALB=Wqy3Dx7zrWGF5hzv35rCfy5DuQrWSBE6x9+ikTcSBREEg5M6b9cXebvR/VgeBg5KKiu0wZoQDrUAUvGjCp9+7Tken9A8Jt5k+/ZF/SB/qLn0THJBBnn9v9qihNAw; Expires=Sun, 15 Sep 2019 16:33:32 GMT; Path=/ | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | Upgrade: websocket | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | Sec-WebSocket-Accept: krsdLig/qcoJqo+TK927ZNCaoQE= | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | Sec-WebSocket-Version: 13 | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | WebSocket-Server: uWebSockets | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | Strict-Transport-Security: max-age=31536000; includeSubDomains | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Server header | | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:33:31.064 BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:33:31.064 Triggering next historical data download in queue. | 2019-09-08 16:33:31.064 Triggering next historical data download in queue. | 2019-09-08 16:33:31.064 Triggering next historical data download in queue. | 2019-09-08 16:33:31.064 Triggering next historical data download in queue. | 2019-09-08 16:33:31.064 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:34.468 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-09-08 16:33:34.468 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:34.468 Connection to the external service has been lost. | 2019-09-08 16:33:34.468 BitMEX Trading Direct socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-09-08 16:33:34.468 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:33:34.468 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:33:34.495 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-09-08 16:33:34.495 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-09-08 16:33:37.500 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-09-08 16:33:37.501 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-09-08 16:33:37.501 BitMEX Trading Direct socket (1) | Connecting to IP: 54.229.111.9. | 2019-09-08 16:33:37.501 BitMEX Trading Direct | Opening WebSocket. | 2019-09-08 16:33:37.684 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-09-08 16:33:37.684 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | Date: Sun, 08 Sep 2019 16:33:39 GMT | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | Connection: upgrade | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | Set-Cookie: AWSALB=CF4yv/qSXY6dsEmLBwKLonDn03HC6MjX/cB3FWPNxds3nf2T4HiiTTDMAz2P6a89MYc8lZnR6rycEKMnx+bRp8m/Kd9+ViBoqHLdONKcnzl1W0pVd4G4VqBuBaIM; Expires=Sun, 15 Sep 2019 16:33:39 GMT; Path=/ | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | Upgrade: websocket | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | Sec-WebSocket-Accept: IL3cVdgwfoxMwCDump/Mk8vc3g8= | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | Sec-WebSocket-Version: 13 | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | WebSocket-Server: uWebSockets | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | Strict-Transport-Security: max-age=31536000; includeSubDomains | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Server header | | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:33:38.322 BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:33:38.322 Triggering next historical data download in queue. | 2019-09-08 16:33:38.322 Triggering next historical data download in queue. | 2019-09-08 16:33:38.322 Triggering next historical data download in queue. | 2019-09-08 16:33:38.323 Triggering next historical data download in queue. | 2019-09-08 16:33:38.323 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:41.709 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-09-08 16:33:41.709 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:41.709 Connection to the external service has been lost. | 2019-09-08 16:33:41.709 BitMEX Trading Direct socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-09-08 16:33:41.709 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:33:41.709 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:33:41.729 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-09-08 16:33:41.729 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-09-08 16:33:44.754 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-09-08 16:33:44.754 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-09-08 16:33:44.755 BitMEX Trading Direct socket (1) | Connecting to IP: 54.229.111.9. | 2019-09-08 16:33:44.755 BitMEX Trading Direct | Opening WebSocket. | 2019-09-08 16:33:44.955 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-09-08 16:33:44.955 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | Date: Sun, 08 Sep 2019 16:33:46 GMT | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | Connection: upgrade | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | Set-Cookie: AWSALB=FE/lLuAIphq/Rap3yr/LsgK2ShZNWun8rimyG/j8PCvRfH1BKOqxYrYFt/91+daCDOb+SGijLL0kEndga6YFA9c3baPrNNiqsrgEqq/z+7Jqr128Wqjngg2TpTeG; Expires=Sun, 15 Sep 2019 16:33:46 GMT; Path=/ | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | Upgrade: websocket | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | Sec-WebSocket-Accept: +Rup6wzym0OJ5k0WTeXdUqtDWEI= | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | Sec-WebSocket-Version: 13 | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | WebSocket-Server: uWebSockets | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | Strict-Transport-Security: max-age=31536000; includeSubDomains | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Server header | | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:33:45.584 BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:33:45.584 Triggering next historical data download in queue. | 2019-09-08 16:33:45.584 Triggering next historical data download in queue. | 2019-09-08 16:33:45.584 Triggering next historical data download in queue. | 2019-09-08 16:33:45.584 Triggering next historical data download in queue. | 2019-09-08 16:33:45.584 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:48.995 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-09-08 16:33:49.192 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:49.192 Connection to the external service has been lost. | 2019-09-08 16:33:49.192 BitMEX Trading Direct socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-09-08 16:33:49.192 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:33:49.192 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:33:49.199 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-09-08 16:33:49.199 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-09-08 16:33:52.204 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-09-08 16:33:52.204 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-09-08 16:33:52.205 BitMEX Trading Direct socket (1) | Connecting to IP: 54.229.111.9. | 2019-09-08 16:33:52.205 BitMEX Trading Direct | Opening WebSocket. | 2019-09-08 16:33:52.380 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-09-08 16:33:52.380 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | Date: Sun, 08 Sep 2019 16:33:54 GMT | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | Connection: upgrade | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | Set-Cookie: AWSALB=Y6emNtJASirNsnO1bNDpaT4ZU1AEfpdhtfmuTfdAN1sVEnl09d12qMkofpJNayb5AnfBSz864F4iEZqf8r6B2Yj+c0NPFaBkcSgJ/XhQ5qG2nUxlEBA+oEdvRWmP; Expires=Sun, 15 Sep 2019 16:33:54 GMT; Path=/ | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | Upgrade: websocket | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | Sec-WebSocket-Accept: pDXf8UwWk4du9z2FrIwOQNc1bjU= | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | Sec-WebSocket-Version: 13 | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | WebSocket-Server: uWebSockets | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | Strict-Transport-Security: max-age=31536000; includeSubDomains | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Server header | | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:33:52.994 BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:33:52.994 Triggering next historical data download in queue. | 2019-09-08 16:33:52.995 Triggering next historical data download in queue. | 2019-09-08 16:33:52.995 Triggering next historical data download in queue. | 2019-09-08 16:33:52.995 Triggering next historical data download in queue. | 2019-09-08 16:33:52.995 File >> Disconnect selected. | 2019-09-08 16:33:54.522 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:54.522 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:54.522 BitMEX Trading Direct socket (1) | Write in progress. Shutdown being delayed. | 2019-09-08 16:33:54.522 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:33:54.522 BitMEX Trading Direct socket (1) | Write has completed. Shutdown being performed. | 2019-09-08 16:33:54.757 BitMEX Trading Direct socket (1) | Shutdown started. Waiting for graceful close. | 2019-09-08 16:33:54.757 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:54.757 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:33:54.757 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-09-08 16:50:41.948 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-09-08 16:50:41.948 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-09-08 16:50:42.160 BitMEX Trading Direct socket (1) | Connecting to IP: 54.229.81.224. | 2019-09-08 16:50:42.161 BitMEX Trading Direct | Opening WebSocket. | 2019-09-08 16:50:43.570 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-09-08 16:50:43.570 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | Date: Sun, 08 Sep 2019 16:50:45 GMT | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | Connection: upgrade | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | Set-Cookie: AWSALB=QG3oXfqiEFA3TBy8oVd8FRAW8mQipz6coghGuQoD6k3YezWaZmiHh8CmcawYvImuETya0RaX8kcODAG6S6tkmADf+xoAElK4VDGeCJ1TCs5WdhDSMgthTT22CZX8; Expires=Sun, 15 Sep 2019 16:50:45 GMT; Path=/ | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | Upgrade: websocket | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | Sec-WebSocket-Accept: JBj3iKhY6QKi7ZjIaopzWyzDB0w= | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | Sec-WebSocket-Version: 13 | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | WebSocket-Server: uWebSockets | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | Strict-Transport-Security: max-age=31536000; includeSubDomains | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Server header | | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:50:44.185 BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:50:44.185 Triggering next historical data download in queue. | 2019-09-08 16:50:44.185 Triggering next historical data download in queue. | 2019-09-08 16:50:44.185 Triggering next historical data download in queue. | 2019-09-08 16:50:44.185 Triggering next historical data download in queue. | 2019-09-08 16:50:44.185 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:50:47.557 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-09-08 16:50:47.557 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:50:47.557 Connection to the external service has been lost. | 2019-09-08 16:50:47.557 BitMEX Trading Direct socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-09-08 16:50:47.557 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:50:47.557 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:50:47.574 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-09-08 16:50:47.574 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-09-08 16:50:50.594 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-09-08 16:50:50.594 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-09-08 16:50:50.595 BitMEX Trading Direct socket (1) | Connecting to IP: 54.229.81.224. | 2019-09-08 16:50:50.595 BitMEX Trading Direct | Opening WebSocket. | 2019-09-08 16:50:50.772 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-09-08 16:50:50.772 BitMEX Trading Direct | Server header | HTTP/1.1 429 Too Many Requests | 2019-09-08 16:50:51.376 BitMEX Trading Direct | Unexpected header. Handshake acknowledgment: HTTP/1.1 429 Too Many Requests. Disconnecting | 2019-09-08 16:50:51.376 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:50:51.376 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2019-09-08 16:50:51.376 Select 'File >> Disconnect' to prevent further connection attempts. | 2019-09-08 16:50:51.376 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:50:51.394 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:50:51.394 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:50:51.394 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-09-08 16:50:51.394 BitMEX Trading Direct socket (1) | Shutdown started. Waiting for graceful close. | 2019-09-08 16:50:51.394 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:50:51.564 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:50:51.564 File >> Disconnect selected. | 2019-09-08 16:50:52.803 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:50:52.803 |
| [2019-09-09 05:53:40] |
| |
|
These are the relevant messages: BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:33:23.830
BitMex is closing the connection for unknown reasons immediately after the connection succeeds. Try creating a new API Key and secret and using those in Sierra Chart. Here are the instructions:BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:33:23.830 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:27.241 Connection to the external service has been lost. | 2019-09-08 16:33:27.241 https://www.sierrachart.com/index.php?page=doc/BitMEX_Trading.php#SetupInstructions Otherwise, we do not see how we can provide more help with this. But we will contact BitMex about this. 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: 2019-09-09 05:54:07
|
| [2019-09-09 08:32:45] |
| greyscape - Posts: 4 |
|
I've been in contact bitmex support of the past few days and they are under the impression the error code you referenced implied the error is on sierras end. I desperately need this resolved. Here is a copy of their response. 288111 is the ticket number. I have reviewed your error logs and found the following. There are no restrictions on your account for API, I would suggest to contact SierraCharts as the connection is being closed client side.
BitMEX Trading Direct | Web socket state is now open. | 2019-09-08 16:33:23.830 BitMEX Trading Direct | Connected to data and trading server. | 2019-09-08 16:33:23.830 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 Triggering next historical data download in queue. | 2019-09-08 16:33:23.831 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | WebSocket closed. | 2019-09-08 16:33:27.241 Connection to the external service has been lost. | 2019-09-08 16:33:27.241 BitMEX Trading Direct socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-09-08 16:33:27.241 BitMEX Trading Direct socket (1) | Closed. | 2019-09-08 16:33:27.241 BitMEX Trading Direct | Disconnected. | 2019-09-08 16:33:27.254 Let us know if you have further questions. Regards, Sen BitMEX |
| [2019-09-09 09:13:32] |
| |
|
this overwhelming exemplifies a billion percent, why we need to have centralized connectivity to BitMex. We should not allow users to connect directly. What you hear from BitMex is nothing but a bunch of garbage.
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: 2019-09-09 09:14:03
|
| [2019-09-09 10:40:18] |
| |
|
We are going to contact BitMex about this . We will hopefully get the issue resolved.
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-09-09 14:48:20] |
| |
|
As we started to go through this to determine what we would give to BitMex in regards to this, we realize we need additional information from you and based on our past experience working with BitMex on these types of issues, we do not think we are going to get any answer as to what the specific problem is. We do have the capability on our side to precisely identify the problem on the client side, and that is simply the BitMex server is closing the connection. We are not sure BitMex has the capability to precisely identify the problem from their side. So our decision at this time, is that we cannot help with this, and we are willing to offer you a refund for the remaining usage time. Let us know how you want to proceed. But we would restate, to re-create a new API key and secret and use those within Sierra Chart. 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: 2019-09-09 14:50:13
|
| [2019-09-09 15:49:01] |
| greyscape - Posts: 4 |
|
I really need to be able to use the Sierra trade services for the different order types. There are no other routes to go here?
Date Time Of Last Edit: 2019-09-10 22:26:04
|
| [2019-09-09 15:59:54] |
| |
|
Did you try creating a new API key? Try doing that two or three times. And removing the old unused keys. Maybe you could create a different BitMex account, and test that one. 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: 2019-09-09 16:00:49
|
| [2019-09-10 03:11:33] |
| |
|
What we want you to do as a test is close all of your Chartbooks and try connecting to BitMex again. Do you notice the connection is continuously getting lost?
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-09-10 11:19:35] |
| |
|
We have been contemplating this issue and we are going to do some additional examination on our side related to this. Please allow about 2 days.
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-09-10 22:04:52] |
| greyscape - Posts: 4 |
|
Hey thank you for continuing to work on this. I posted a reply yesterday but it doesn't look like it went through. Deleting the old api keys did the trick. That might be something you guys could add to the trade service trouble shooting page for non technical people like me. I didn't even think to delete the old api keys. Thanks again
|
| [2019-09-10 22:18:34] |
| |
|
Yes we will make a note of that. So that confirms, this was strictly a BitMex issue all along and there is something going wrong on their 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2019-09-10 22:18:41
|
To post a message in this thread, you need to log in with your Sierra Chart account: