Login Page - Create Account

Support Board


Date/Time: Sat, 04 May 2024 05:24:06 +0000



Post From: Unable to access Bitmex

[2018-03-17 05:19:13]
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
imagefurther log another attempt.jpg / V - Attached On 2018-03-17 05:18:51 UTC - Size: 225.37 KB - 369 views