Home >> Support Board

Support Board

Date/Time: Tue, 23 Apr 2024 12:55:20 +0000

How to Post a Message for Support

Unable to access Bitmex

View Count: 2046

[2018-03-16 03:37:58] #1 [Go To First Post]
Wendys - Posts: 9
I cannot access Bitmex. I have followed all the instructions in creating an API on the Bitmex website and setting it up in Sierra Chart. I have already disconnected and reconnected. I have disabled my firewall. I have created new API keys and I am using those. I have updated the symbol settings and reset the symbol settings. I have rebooted my computer. I have waited. I have tried using the 64-bit version and the standard version. I have sent the log in via Sierra Chart application. This is the log: Reading Internal Order ID file. \| 2018-03-16 03:36:01 Reading Trade Orders file. \| 2018-03-16 03:36:01 Reading Trade Positions file. \| 2018-03-16 03:36:01 Listening on UDP port 22904. \| 2018-03-16 03:36:01 Software version: 1717 64-bit \| 2018-03-16 03:36:01 Usage end date: 2018-03-31 \| 2018-03-16 03:36:01 Enabled for: Advanced Features. \| 2018-03-16 03:36:01 Enabled for: Advanced Features 2. \| 2018-03-16 03:36:01 Enabled for: Sierra Chart Historical Data Service. \| 2018-03-16 03:36:01 Allow Support for Sierra Chart Data Feeds is enabled. \| 2018-03-16 03:36:01 Current selected Data/Trading service: BitMEX Trading Direct \| 2018-03-16 03:36:01 Chart Update Interval: 500 \| 2018-03-16 03:36:01 Time Zone: +00:00:00 (UTC+00) \| 2018-03-16 03:36:01 2018-03-15 20:36:00 Local computer time \| 2018-03-16 03:36:01 2018-03-16 03:36:00 Local computer time in UTC \| 2018-03-16 03:36:01 2018-03-16 03:36:00 Local computer time in SC Time Zone \| 2018-03-16 03:36:01 2018-03-16 03:36:08 Server time in UTC \| 2018-03-16 03:36:01 Local computer UTC time and Server UTC time difference: 8 seconds. \| 2018-03-16 03:36:01 Program path: C:\SierraChart\ \| 2018-03-16 03:36:01 Data Files path: C:\SierraChart\Data\ \| 2018-03-16 03:36:01 OS Version Number: 6.1 \| 2018-03-16 03:36:01 Locale Setting: C \| 2018-03-16 03:36:01 Checking for new symbol settings for service code bitmex.dtc.trading \| 2018-03-16 03:36:01 HTTPS connection to www.sierrachart.com:443 (4) \| Creating socket. Using TLS 1.2. \| 2018-03-16 03:36:01 HTTPS connection to www.sierrachart.com:443 (4) \| Connecting to IP: 204.15.192.108. \| 2018-03-16 03:36:01 Symbol settings are up-to-date for bitmex.dtc.trading \| 2018-03-16 03:36:01 Received 5 login tokens. \| 2018-03-16 03:36:01 BitMEX Trading Direct \| Connecting to URI testnet.bitmex.com/realtime/WebSocket \| 2018-03-16 03:36:05 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 03:36:05 BitMEX WebSocket socket (5) \| Creating socket. Using TLS 1.2. \| 2018-03-16 03:36:05 BitMEX WebSocket socket (5) \| Connecting to IP: 54.76.252.17. \| 2018-03-16 03:36:05 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 03:36:05 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. HTTP/1.1 101 Switching Protocols \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 03:36:12 GMT \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. Connection: upgrade \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. Upgrade: websocket \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. Sec-WebSocket-Accept: HQr6jpeV/LIBeNa+4rl3Y4rL40Y= \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. Sec-WebSocket-Version: 13 \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. WebSocket-Server: uWebSockets \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 03:36:05 BitMEX WebSocket \| Header line. \| 2018-03-16 03:36:05 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 03:36:05 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 03:36:05 BitMEX WebSocket socket (5) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:05 BitMEX WebSocket socket (5) \| Received socket Close event. \| 2018-03-16 03:36:05 BitMEX WebSocket \| WebSocket received OpCode Close. Received status code: 0 \| 2018-03-16 03:36:05 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:05 Connection to the external service has been lost. \| 2018-03-16 03:36:05 BitMEX WebSocket socket (5) \| Initiating close of socket by core. \| 2018-03-16 03:36:05 BitMEX WebSocket \| Network socket for WebSocket has been closed by remote side. \| 2018-03-16 03:36:05 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:05 BitMEX WebSocket socket (5) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 03:36:05 BitMEX WebSocket socket (5) \| Closed. \| 2018-03-16 03:36:05 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 03:36:05 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:05 HTTPS connection to www.sierrachart.com:443 (4) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (4) \| Received socket Close event. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (4) \| Initiating close of socket by core. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (4) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (4) \| Closed. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (2) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (2) \| Received socket Close event. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (2) \| Initiating close of socket by core. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (2) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 03:36:06 HTTPS connection to www.sierrachart.com:443 (2) \| Closed. \| 2018-03-16 03:36:06 BitMEX Trading Direct \| Connecting to URI testnet.bitmex.com/realtime/WebSocket \| 2018-03-16 03:36:08 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 03:36:08 BitMEX WebSocket socket (6) \| Creating socket. Using TLS 1.2. \| 2018-03-16 03:36:08 BitMEX WebSocket socket (6) \| Connecting to IP: 54.76.252.17. \| 2018-03-16 03:36:08 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 03:36:08 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. HTTP/1.1 101 Switching Protocols \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 03:36:16 GMT \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. Connection: upgrade \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. Upgrade: websocket \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. Sec-WebSocket-Accept: T1xjoorPSQRJdvu6eHftOcoNuv4= \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. Sec-WebSocket-Version: 13 \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. WebSocket-Server: uWebSockets \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 03:36:08 BitMEX WebSocket \| Header line. \| 2018-03-16 03:36:08 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 03:36:08 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 03:36:08 BitMEX WebSocket socket (6) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:08 BitMEX WebSocket \| WebSocket received OpCode Close. Received status code: 0 \| 2018-03-16 03:36:08 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:08 Connection to the external service has been lost. \| 2018-03-16 03:36:08 BitMEX WebSocket socket (6) \| Received socket Close event. \| 2018-03-16 03:36:08 BitMEX WebSocket socket (6) \| Initiating close of socket by core. \| 2018-03-16 03:36:08 BitMEX WebSocket \| Network socket for WebSocket has been closed by remote side. \| 2018-03-16 03:36:08 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:08 BitMEX WebSocket socket (6) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 03:36:08 BitMEX WebSocket socket (6) \| Closed. \| 2018-03-16 03:36:08 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 03:36:08 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:08 BitMEX Trading Direct \| Connecting to URI testnet.bitmex.com/realtime/WebSocket \| 2018-03-16 03:36:11 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Creating socket. Using TLS 1.2. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Connecting to IP: 54.76.252.17. \| 2018-03-16 03:36:11 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 03:36:11 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 03:36:11 BitMEX WebSocket \| Header line. HTTP/1.1 429 Too Many Requests \| 2018-03-16 03:36:11 BitMEX WebSocket \| WebSocket not connected. Handshake acknowledgment: HTTP/1.1 429 Too Many Requests \| 2018-03-16 03:36:11 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:11 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2018-03-16 03:36:11 Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:11 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 03:36:19 GMT \| 2018-03-16 03:36:11 BitMEX WebSocket \| Header line. Content-Type: application/json \| 2018-03-16 03:36:11 BitMEX WebSocket \| Header line. Content-Length: 52 \| 2018-03-16 03:36:11 BitMEX WebSocket \| Header line. Connection: keep-alive \| 2018-03-16 03:36:11 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 03:36:11 BitMEX WebSocket \| Header line. \| 2018-03-16 03:36:11 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 03:36:11 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 03:36:11 BitMEX WebSocket \| Extension reserve bits set and not supported. \| 2018-03-16 03:36:11 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:11 Connection to the external service has been lost. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Adding bytes from final send buffer from buffered socket: 8 \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Initiating close of socket by core. \| 2018-03-16 03:36:11 BitMEX WebSocket \| WebSocket closed. \| 2018-03-16 03:36:11 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Sending bytes from final send buffer: 8 \| 2018-03-16 03:36:11 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 03:36:11 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Write in progress. Shutdown being delayed. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Write has completed. Shutdown being performed. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Shutdown started. Waiting for graceful close. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:11 BitMEX WebSocket socket (7) \| Closed. \| 2018-03-16 03:36:11 BitMEX Trading Direct \| Connecting to URI testnet.bitmex.com/realtime/WebSocket \| 2018-03-16 03:36:14 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Creating socket. Using TLS 1.2. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Connecting to IP: 54.76.252.17. \| 2018-03-16 03:36:14 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 03:36:14 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 03:36:14 BitMEX WebSocket \| Header line. HTTP/1.1 429 Too Many Requests \| 2018-03-16 03:36:14 BitMEX WebSocket \| WebSocket not connected. Handshake acknowledgment: HTTP/1.1 429 Too Many Requests \| 2018-03-16 03:36:14 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:14 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2018-03-16 03:36:14 Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:14 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 03:36:22 GMT \| 2018-03-16 03:36:14 BitMEX WebSocket \| Header line. Content-Type: application/json \| 2018-03-16 03:36:14 BitMEX WebSocket \| Header line. Content-Length: 52 \| 2018-03-16 03:36:14 BitMEX WebSocket \| Header line. Connection: keep-alive \| 2018-03-16 03:36:14 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 03:36:14 BitMEX WebSocket \| Header line. \| 2018-03-16 03:36:14 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 03:36:14 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 03:36:14 BitMEX WebSocket \| Extension reserve bits set and not supported. \| 2018-03-16 03:36:14 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:14 Connection to the external service has been lost. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Adding bytes from final send buffer from buffered socket: 8 \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Initiating close of socket by core. \| 2018-03-16 03:36:14 BitMEX WebSocket \| WebSocket closed. \| 2018-03-16 03:36:14 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Sending bytes from final send buffer: 8 \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Write in progress. Shutdown being delayed. \| 2018-03-16 03:36:14 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 03:36:14 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Write has completed. Shutdown being performed. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Shutdown started. Waiting for graceful close. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:14 BitMEX WebSocket socket (8) \| Closed. \| 2018-03-16 03:36:14 BitMEX Trading Direct \| Connecting to URI testnet.bitmex.com/realtime/WebSocket \| 2018-03-16 03:36:17 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 03:36:17 BitMEX WebSocket socket (9) \| Creating socket. Using TLS 1.2. \| 2018-03-16 03:36:17 BitMEX WebSocket socket (9) \| Connecting to IP: 54.76.252.17. \| 2018-03-16 03:36:17 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 03:36:17 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. HTTP/1.1 101 Switching Protocols \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 03:36:25 GMT \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. Connection: upgrade \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. Upgrade: websocket \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. Sec-WebSocket-Accept: 5gkrD3JksjU+hQ+4kq05cF4Rqq4= \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. Sec-WebSocket-Version: 13 \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. WebSocket-Server: uWebSockets \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 03:36:17 BitMEX WebSocket \| Header line. \| 2018-03-16 03:36:17 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 03:36:17 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 03:36:17 BitMEX WebSocket socket (9) \| Received socket Close event. \| 2018-03-16 03:36:17 BitMEX WebSocket socket (9) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:17 BitMEX WebSocket \| WebSocket received OpCode Close. Received status code: 0 \| 2018-03-16 03:36:17 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:17 Connection to the external service has been lost. \| 2018-03-16 03:36:17 BitMEX WebSocket socket (9) \| Initiating close of socket by core. \| 2018-03-16 03:36:17 BitMEX WebSocket \| Network socket for WebSocket has been closed by remote side. \| 2018-03-16 03:36:17 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:17 BitMEX WebSocket socket (9) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 03:36:17 BitMEX WebSocket socket (9) \| Closed. \| 2018-03-16 03:36:17 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 03:36:17 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:17 BitMEX Trading Direct \| Connecting to URI testnet.bitmex.com/realtime/WebSocket \| 2018-03-16 03:36:21 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Creating socket. Using TLS 1.2. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Connecting to IP: 54.76.252.17. \| 2018-03-16 03:36:21 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 03:36:21 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 03:36:21 BitMEX WebSocket \| Header line. HTTP/1.1 429 Too Many Requests \| 2018-03-16 03:36:21 BitMEX WebSocket \| WebSocket not connected. Handshake acknowledgment: HTTP/1.1 429 Too Many Requests \| 2018-03-16 03:36:21 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:21 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. \| 2018-03-16 03:36:21 Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:21 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 03:36:28 GMT \| 2018-03-16 03:36:21 BitMEX WebSocket \| Header line. Content-Type: application/json \| 2018-03-16 03:36:21 BitMEX WebSocket \| Header line. Content-Length: 53 \| 2018-03-16 03:36:21 BitMEX WebSocket \| Header line. Connection: keep-alive \| 2018-03-16 03:36:21 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 03:36:21 BitMEX WebSocket \| Header line. \| 2018-03-16 03:36:21 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 03:36:21 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 03:36:21 BitMEX WebSocket \| Extension reserve bits set and not supported. \| 2018-03-16 03:36:21 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:21 Connection to the external service has been lost. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Adding bytes from final send buffer from buffered socket: 8 \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Initiating close of socket by core. \| 2018-03-16 03:36:21 BitMEX WebSocket \| WebSocket closed. \| 2018-03-16 03:36:21 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Sending bytes from final send buffer: 8 \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Write in progress. Shutdown being delayed. \| 2018-03-16 03:36:21 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 03:36:21 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Write has completed. Shutdown being performed. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Shutdown started. Waiting for graceful close. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Socket gracefully closed by remote side. \| 2018-03-16 03:36:21 BitMEX WebSocket socket (10) \| Closed. \| 2018-03-16 03:36:21 File >> Disconnect selected. \| 2018-03-16 03:36:23 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 03:36:23

[2018-03-16 05:50:41] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We cannot say exactly what the reason for the problem is because the connection is being denied by BitMEX. What we recommend you do is wait a few hours, create a new API Key and secret through your BitMEX account, enter those into Sierra Chart and try again. We expect hopefully by no later than mid April, to use a different connectivity method which will completely eliminate this problem altogether. 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

[2018-03-16 06:02:12] #3 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Also we are going to come out with version 1718 we expect by the middle of the day. We will want you to test that and and provide the Message Log because there is a problem we are seeing, which is not the underlying issue, which needs to get resolved and we hope it should be resolved in the next release but we thought it already was in 1717. 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

[2018-03-16 20:36:49] #4 [Go To First Post]
Wendys - Posts: 9
I believe I am making progress. When attempting to connect to the live server, I get the following log. This repeats itself. Reading Internal Order ID file. \| 2018-03-16 20:24:41 Reading Trade Orders file. \| 2018-03-16 20:24:41 Reading Trade Positions file. \| 2018-03-16 20:24:41 Listening on UDP port 22904. \| 2018-03-16 20:24:41 Software version: 1717 64-bit \| 2018-03-16 20:24:41 Usage end date: 2018-03-31 \| 2018-03-16 20:24:41 Enabled for: Advanced Features. \| 2018-03-16 20:24:41 Enabled for: Advanced Features 2. \| 2018-03-16 20:24:41 Enabled for: Sierra Chart Historical Data Service. \| 2018-03-16 20:24:41 Allow Support for Sierra Chart Data Feeds is enabled. \| 2018-03-16 20:24:41 Current selected Data/Trading service: BitMEX Trading Direct \| 2018-03-16 20:24:41 Chart Update Interval: 500 \| 2018-03-16 20:24:41 Time Zone: +00:00:00 (UTC+00) \| 2018-03-16 20:24:41 2018-03-16 13:24:40 Local computer time \| 2018-03-16 20:24:41 2018-03-16 20:24:40 Local computer time in UTC \| 2018-03-16 20:24:41 2018-03-16 20:24:40 Local computer time in SC Time Zone \| 2018-03-16 20:24:41 2018-03-16 20:24:40 Server time in UTC \| 2018-03-16 20:24:41 Local computer UTC time and Server UTC time difference: 0 seconds. \| 2018-03-16 20:24:41 Program path: C:\SierraChart\ \| 2018-03-16 20:24:41 Data Files path: C:\SierraChart\Data\ \| 2018-03-16 20:24:41 OS Version Number: 6.1 \| 2018-03-16 20:24:41 Locale Setting: C \| 2018-03-16 20:24:41 Checking for new symbol settings for service code bitmex.dtc.trading \| 2018-03-16 20:24:41 HTTPS connection to www.sierrachart.com:443 (4) \| Creating socket. Using TLS 1.2. \| 2018-03-16 20:24:41 HTTPS connection to www.sierrachart.com:443 (4) \| Connecting to IP: 204.15.192.108. \| 2018-03-16 20:24:41 Symbol settings are up-to-date for bitmex.dtc.trading \| 2018-03-16 20:24:41 Received 5 login tokens. \| 2018-03-16 20:24:41 BitMEX Trading Direct \| Connecting to URI www.bitmex.com/realtime/WebSocket \| 2018-03-16 20:24:45 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 20:24:45 BitMEX WebSocket socket (5) \| Creating socket. Using TLS 1.2. \| 2018-03-16 20:24:45 BitMEX WebSocket socket (5) \| Connecting to IP: 52.30.29.6. \| 2018-03-16 20:24:45 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 20:24:45 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. HTTP/1.1 101 Switching Protocols \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 20:24:45 GMT \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. Connection: upgrade \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. Set-Cookie: AWSALB=jK4IJQN/tX/oCMvl3Tg7sfaJ3w5ekepX7AFeQ6fl3E0jRqrwHe3JGDPQLGKxO7GknDX8SnyOv3g/vH3CwJwvP7+5Gu1q7L951JgdDYA4RCN/cW7itB+88xZdGaFs; Expires=Fri, 23 Mar 2018 20:24:45 GMT; Path=/ \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. Upgrade: websocket \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. Sec-WebSocket-Accept: 7XeYR6CIER7qxf4pi8MSHYgGA5I= \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. Sec-WebSocket-Version: 13 \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. WebSocket-Server: uWebSockets \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 20:24:45 BitMEX WebSocket \| Header line. \| 2018-03-16 20:24:45 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 20:24:45 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 20:24:45 HTTPS connection to www.sierrachart.com:443 (4) \| Socket gracefully closed by remote side. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (4) \| Received socket Close event. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (4) \| Initiating close of socket by core. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (4) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (4) \| Closed. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (2) \| Socket gracefully closed by remote side. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (2) \| Received socket Close event. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (2) \| Initiating close of socket by core. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (2) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 20:24:46 HTTPS connection to www.sierrachart.com:443 (2) \| Closed. \| 2018-03-16 20:24:46 HTTPS connection to www.bitmex.com:443 (6) \| Creating socket. Using TLS 1.2. \| 2018-03-16 20:24:50 HTTPS connection to www.bitmex.com:443 (6) \| Connecting to IP: 52.30.29.6. \| 2018-03-16 20:24:50 HTTPS connection to www.bitmex.com:443 (6) \| Received socket Close event. \| 2018-03-16 20:27:49 HTTPS connection to www.bitmex.com:443 (6) \| Socket gracefully closed by remote side. \| 2018-03-16 20:27:49 HTTPS connection to www.bitmex.com:443 (6) \| Initiating close of socket by core. \| 2018-03-16 20:27:49 HTTPS connection to www.bitmex.com:443 (6) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-16 20:27:49 HTTPS connection to www.bitmex.com:443 (6) \| Closed. \| 2018-03-16 20:27:49 The data feed was lost. There was no activity for at least 10.0 minutes. \| 2018-03-16 20:34:51 Connection to the external service has been lost. \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Adding bytes from final send buffer from buffered socket: 8 \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Initiating close of socket by core. \| 2018-03-16 20:34:51 BitMEX WebSocket \| WebSocket closed. \| 2018-03-16 20:34:51 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Sending bytes from final send buffer: 8 \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Write in progress. Shutdown being delayed. \| 2018-03-16 20:34:51 BitMEX Trading Direct \| Disconnected. \| 2018-03-16 20:34:51 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Write has completed. Shutdown being performed. \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Shutdown started. Waiting for graceful close. \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Socket gracefully closed by remote side. \| 2018-03-16 20:34:51 BitMEX WebSocket socket (5) \| Closed. \| 2018-03-16 20:34:51 BitMEX Trading Direct \| Connecting to URI www.bitmex.com/realtime/WebSocket \| 2018-03-16 20:34:54 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-16 20:34:54 BitMEX WebSocket socket (17) \| Creating socket. Using TLS 1.2. \| 2018-03-16 20:34:54 BitMEX WebSocket socket (17) \| Connecting to IP: 54.77.104.17. \| 2018-03-16 20:34:54 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-16 20:34:54 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. HTTP/1.1 101 Switching Protocols \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. Date: Fri, 16 Mar 2018 20:34:56 GMT \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. Connection: upgrade \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. Set-Cookie: AWSALB=e+APGA5TjN5hcYNCTDXX2RIabctvfqOwzmOu9utJVVEsOxBt+TeIUUUcNt8106pEqww5F7lBiJyx2ocbYG2HguKm8UQKyaUZn27Sxhsx5l4XW1DTIEbOgH2d5Lcv; Expires=Fri, 23 Mar 2018 20:34:56 GMT; Path=/ \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. Upgrade: websocket \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. Sec-WebSocket-Accept: zvqArrofkwy+gtUhoTboLheF9uM= \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. Sec-WebSocket-Version: 13 \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. WebSocket-Server: uWebSockets \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-16 20:34:54 BitMEX WebSocket \| Header line. \| 2018-03-16 20:34:54 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-16 20:34:54 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-16 20:34:54 HTTPS connection to www.bitmex.com:443 (18) \| Creating socket. Using TLS 1.2. \| 2018-03-16 20:34:59 HTTPS connection to www.bitmex.com:443 (18) \| Connecting to IP: 54.77.104.17. \| 2018-03-16 20:34:59

[2018-03-17 01:49:59] #5 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The connection is now successful. Follow step #11 here to open a chart: https://www.sierrachart.com/index.php?page=doc/BitMEX_Trading.php#SetupInstructions 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

[2018-03-17 02:56:24] #6 [Go To First Post]
Wendys - Posts: 9
Thank you for your prompt response. Unfortunately, it does this for several minutes, then gracefully closes the terminal.

[2018-03-17 05:19:13] #7 [Go To First Post]
Wendys - Posts: 9
I made bold the line you are reading, the last line of the log according to the above post. Everything that occurs after that in the log is what happens next. This happens every time. I have not been able to connect to Bitmex once yet. Reading Internal Order ID file. \| 2018-03-17 05:09:31 Reading Trade Orders file. \| 2018-03-17 05:09:31 Reading Trade Positions file. \| 2018-03-17 05:09:31 Listening on UDP port 22904. \| 2018-03-17 05:09:31 Software version: 1717 64-bit \| 2018-03-17 05:09:31 Usage end date: 2018-03-31 \| 2018-03-17 05:09:31 Enabled for: Advanced Features. \| 2018-03-17 05:09:31 Enabled for: Advanced Features 2. \| 2018-03-17 05:09:31 Enabled for: Sierra Chart Historical Data Service. \| 2018-03-17 05:09:31 Allow Support for Sierra Chart Data Feeds is enabled. \| 2018-03-17 05:09:31 Current selected Data/Trading service: BitMEX Trading Direct \| 2018-03-17 05:09:31 Chart Update Interval: 500 \| 2018-03-17 05:09:31 Time Zone: +00:00:00 (UTC+00) \| 2018-03-17 05:09:31 2018-03-16 22:09:31 Local computer time \| 2018-03-17 05:09:31 2018-03-17 05:09:31 Local computer time in UTC \| 2018-03-17 05:09:31 2018-03-17 05:09:31 Local computer time in SC Time Zone \| 2018-03-17 05:09:31 2018-03-17 05:09:51 Server time in UTC \| 2018-03-17 05:09:31 Local computer UTC time and Server UTC time difference: 21 seconds. \| 2018-03-17 05:09:31 Program path: C:\SierraChart\ \| 2018-03-17 05:09:31 Data Files path: C:\SierraChart\Data\ \| 2018-03-17 05:09:31 OS Version Number: 6.1 \| 2018-03-17 05:09:31 Locale Setting: C \| 2018-03-17 05:09:31 Checking for new symbol settings for service code bitmex.dtc.trading \| 2018-03-17 05:09:31 HTTPS connection to www.sierrachart.com:443 (4) \| Creating socket. Using TLS 1.2. \| 2018-03-17 05:09:31 HTTPS connection to www.sierrachart.com:443 (4) \| Connecting to IP: 204.15.192.108. \| 2018-03-17 05:09:31 Symbol settings are up-to-date for bitmex.dtc.trading \| 2018-03-17 05:09:32 Received 5 login tokens. \| 2018-03-17 05:09:32 BitMEX Trading Direct \| Connecting to URI www.bitmex.com/realtime/WebSocket \| 2018-03-17 05:09:35 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-17 05:09:35 BitMEX WebSocket socket (5) \| Creating socket. Using TLS 1.2. \| 2018-03-17 05:09:35 BitMEX WebSocket socket (5) \| Connecting to IP: 54.229.45.10. \| 2018-03-17 05:09:35 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-17 05:09:35 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-17 05:09:35 BitMEX WebSocket \| Header line. HTTP/1.1 101 Switching Protocols \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. Date: Sat, 17 Mar 2018 05:09:56 GMT \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. Connection: upgrade \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. Set-Cookie: AWSALB=10bdMo9zzjJN5sgiOSidT0URUJ0NWmD5xPA+clyhmw1bY8yIi8wGu2/qTjtqDcZzWk3lifw44OkLfs0R3U6jqO+pGA2DI5VqeICiYvgI9+wndl+8PnVDTBVWITDd; Expires=Sat, 24 Mar 2018 05:09:56 GMT; Path=/ \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. Upgrade: websocket \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. Sec-WebSocket-Accept: cqJUc1O3zYTNwWGR+UKbjwvArfg= \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. Sec-WebSocket-Version: 13 \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. WebSocket-Server: uWebSockets \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-17 05:09:36 BitMEX WebSocket \| Header line. \| 2018-03-17 05:09:36 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-17 05:09:36 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-17 05:09:36 BitMEX WebSocket socket (5) \| Received socket Close event. \| 2018-03-17 05:09:36 BitMEX WebSocket socket (5) \| Socket gracefully closed by remote side. \| 2018-03-17 05:09:36 BitMEX WebSocket socket (5) \| 2 bytes remaining in receive buffer when socket closed. \| 2018-03-17 05:09:36 BitMEX WebSocket socket (5) \| Initiating close of socket by core. \| 2018-03-17 05:09:36 BitMEX WebSocket \| Network socket for WebSocket has been closed by remote side. \| 2018-03-17 05:09:36 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-17 05:09:36 Connection to the external service has been lost. \| 2018-03-17 05:09:36 BitMEX WebSocket socket (5) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-17 05:09:36 BitMEX WebSocket socket (5) \| Closed. \| 2018-03-17 05:09:36 BitMEX Trading Direct \| Disconnected. \| 2018-03-17 05:09:36 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2018-03-17 05:09:36 HTTPS connection to www.sierrachart.com:443 (4) \| Socket gracefully closed by remote side. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (4) \| Received socket Close event. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (4) \| Initiating close of socket by core. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (4) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (4) \| Closed. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (2) \| Socket gracefully closed by remote side. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (2) \| Received socket Close event. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (2) \| Initiating close of socket by core. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (2) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-17 05:09:37 HTTPS connection to www.sierrachart.com:443 (2) \| Closed. \| 2018-03-17 05:09:37 File >> Disconnect selected. \| 2018-03-17 05:09:37 BitMEX Trading Direct \| Disconnected. \| 2018-03-17 05:09:37 BitMEX Trading Direct \| Connecting to URI www.bitmex.com/realtime/WebSocket \| 2018-03-17 05:10:12 BitMEX WebSocket \| Connecting to WebSocket server. \| 2018-03-17 05:10:12 BitMEX WebSocket socket (6) \| Creating socket. Using TLS 1.2. \| 2018-03-17 05:10:12 BitMEX WebSocket socket (6) \| Connecting to IP: 54.229.45.10. \| 2018-03-17 05:10:12 BitMEX WebSocket \| Opening WebSocket. \| 2018-03-17 05:10:12 BitMEX WebSocket \| Sending WebSocket handshake. \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. HTTP/1.1 101 Switching Protocols \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. Date: Sat, 17 Mar 2018 05:10:33 GMT \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. Connection: upgrade \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. Set-Cookie: AWSALB=tHTc4JZfIYmMAspZTRuJ0QvSUwJGR+oi6+ZLIJzdaO2qWT+uFNP/tEruJpF2WodSbECX+vNjJ0KuIWayvllJBiAxn1EilfUHo9cZ/c1x44+CeagkK1QI06KOnxkD; Expires=Sat, 24 Mar 2018 05:10:33 GMT; Path=/ \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. Upgrade: websocket \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. Sec-WebSocket-Accept: jovXKF+aezgisZzquo0EJh1MZOY= \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. Sec-WebSocket-Version: 13 \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. WebSocket-Server: uWebSockets \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains \| 2018-03-17 05:10:12 BitMEX WebSocket \| Header line. \| 2018-03-17 05:10:12 BitMEX WebSocket \| Web socket state is now open. \| 2018-03-17 05:10:12 BitMEX Trading Direct \| Connected to data and trading server. \| 2018-03-17 05:10:12 HTTPS connection to www.bitmex.com:443 (7) \| Creating socket. Using TLS 1.2. \| 2018-03-17 05:10:17 HTTPS connection to www.bitmex.com:443 (7) \| Connecting to IP: 54.229.45.10. \| 2018-03-17 05:10:17 HTTPS connection to www.bitmex.com:443 (7) \| Received socket Close event. \| 2018-03-17 05:13:17 HTTPS connection to www.bitmex.com:443 (7) \| Socket gracefully closed by remote side. \| 2018-03-17 05:13:17 HTTPS connection to www.bitmex.com:443 (7) \| Initiating close of socket by core. \| 2018-03-17 05:13:17 HTTPS connection to www.bitmex.com:443 (7) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2018-03-17 05:13:17 HTTPS connection to www.bitmex.com:443 (7) \| Closed. \| 2018-03-17 05:13:17 File >> Disconnect selected. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Adding bytes from final send buffer from buffered socket: 8 \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Initiating close of socket by core. \| 2018-03-17 05:13:43 BitMEX WebSocket \| WebSocket closed. \| 2018-03-17 05:13:43 BitMEX Trading Direct \| WebSocket closed. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Sending bytes from final send buffer: 8 \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Write in progress. Shutdown being delayed. \| 2018-03-17 05:13:43 BitMEX Trading Direct \| Disconnected. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Write has completed. Shutdown being performed. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Shutdown started. Waiting for graceful close. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Received socket Close event. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Still waiting for graceful close or receive error. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Socket gracefully closed by remote side. \| 2018-03-17 05:13:43 BitMEX WebSocket socket (6) \| Closed. \| 2018-03-17 05:13:43


further log another attempt.jpg / V - Attached On 2018-03-17 05:18:51 UTC - Size: 225.37 KB - 368 views

[2018-03-17 10:57:27] #8 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Refer to: Notice: Policy Regarding BitMEX Connection Issues 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

[2018-03-19 16:32:27] #9 [Go To First Post]
Wendys - Posts: 9
I have submitted a support ticket to Bitmex, and I am awaiting their reply. I am hoping they will be able to assist me from their side, today or in the next couple of days, so I will not have to put a hold on my account.

[2018-03-19 20:21:43] #10 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
For now you can use BitMEX market data by following the instructions here: Cryptocurrency / Bitcoin Data and Trading Services 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

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