Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 10 May 2024 20:48:18 +0000
Can't connect to BitMEX
View Count: 1808
| [2018-08-12 19:31:24] |
| User683734 - Posts: 3 |
|
I am currently in Trial period and i am interested in buying your service (for OTO orders) but only if i can make it run on BitMEX. I followed the instructions on both bitmex and your site and i'm getting this error. I couldn't find a workaround in your FAQ. I edited out auth keys Software version: 1785 64-bit | 2018-08-12 22:23:56 Usage end date: 2018-08-27 | 2018-08-12 22:23:56 Enabled for: Advanced Features. | 2018-08-12 22:23:56 Enabled for: Advanced Features 2. | 2018-08-12 22:23:56 Enabled for: Sierra Chart Historical Data Service. | 2018-08-12 22:23:56 Allow Support for Sierra Chart Data Feeds is enabled. | 2018-08-12 22:23:56 Current selected Data/Trading service: BitMEX Trading Direct | 2018-08-12 22:23:56 Chart Update Interval: 500 | 2018-08-12 22:23:56 Time Zone: +03:00:00 (EET+02EEST+01,M3.5.0/03:00,M10.5.0/04:00) | 2018-08-12 22:23:56 2018-08-12 22:23:56 Local computer time | 2018-08-12 22:23:56 2018-08-12 19:23:56 Local computer time in UTC | 2018-08-12 22:23:56 2018-08-12 22:23:56 Local computer time in SC Time Zone | 2018-08-12 22:23:56 2018-08-12 19:18:11 Server time in UTC | 2018-08-12 22:23:56 Local computer UTC time and Server UTC time difference: 2 seconds. | 2018-08-12 22:23:56 Program path: C:\SierraChart\ | 2018-08-12 22:23:56 Data Files path: C:\SierraChart\Data\ | 2018-08-12 22:23:56 OS Version Number: 10.0 | 2018-08-12 22:23:56 Locale Setting: C | 2018-08-12 22:23:56 BitMEX Trading Direct | Connecting to URI testnet.bitmex.com/realtime/WebSocket | 2018-08-12 22:23:58 BitMEX WebSocket | Connecting to WebSocket server. | 2018-08-12 22:23:58 BitMEX WebSocket socket (15) | Creating socket. Using TLS 1.2. | 2018-08-12 22:23:58 BitMEX WebSocket socket (15) | Connecting to IP: 104.18.119.87. | 2018-08-12 22:23:58 BitMEX WebSocket | Opening WebSocket. | 2018-08-12 22:23:58 BitMEX WebSocket | Sending WebSocket handshake. | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. HTTP/1.1 101 Switching Protocols | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Date: Sun, 12 Aug 2018 19:23:59 GMT | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Connection: upgrade | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Set-Cookie: __cfduid=d23153d7a0d39cc73750d1bc8a60286e41534101839; expires=Mon, 12-Aug-19 19:23:59 GMT; path=/; domain=.bitmex.com; HttpOnly; Secure | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Upgrade: websocket | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Sec-WebSocket-Accept: 1z6HCJZsM1ibkQTqcopwm66YLFY= | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Sec-WebSocket-Version: 13 | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. WebSocket-Server: uWebSockets | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Strict-Transport-Security: max-age=31536000; includeSubDomains | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. Server: cloudflare | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. CF-RAY: 449551d25a917efa-BUD | 2018-08-12 22:23:58 BitMEX WebSocket | Header line. | 2018-08-12 22:23:58 BitMEX WebSocket | Web socket state is now open. | 2018-08-12 22:23:58 BitMEX Trading Direct | Connected to data and trading server. | 2018-08-12 22:23:58 BitMEX Trading Direct | | 2018-08-12 22:23:58 BitMEX Trading Direct | ---------------- Outgoing web socket message: ---------------- | 2018-08-12 22:23:58 BitMEX Trading Direct | {"op": "authKey", "args": ["x", 3743263438086, "x"]} | 2018-08-12 22:23:58 BitMEX WebSocket socket (15) | Received socket Close event. | 2018-08-12 22:23:58 BitMEX WebSocket socket (15) | Socket gracefully closed by remote side. | 2018-08-12 22:23:58 BitMEX WebSocket | WebSocket received OpCode Close. Received status code: 0 | 2018-08-12 22:23:58 BitMEX Trading Direct | WebSocket closed. | 2018-08-12 22:23:58 Connection to the external service has been lost. | 2018-08-12 22:23:58 BitMEX WebSocket socket (15) | Initiating close of socket by core. | 2018-08-12 22:23:58 BitMEX WebSocket | Network socket for WebSocket has been closed by remote side. | 2018-08-12 22:23:58 BitMEX WebSocket socket (15) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-08-12 22:23:58 BitMEX Trading Direct | WebSocket closed. | 2018-08-12 22:23:58 BitMEX WebSocket socket (15) | Closed. | 2018-08-12 22:23:58 BitMEX Trading Direct | Disconnected. | 2018-08-12 22:23:58 |
| [2018-08-12 20:40:18] |
| |
|
BitMEX WebSocket socket (15) | Received socket Close event. | 2018-08-12 22:23:58 These lines indicate that BitMex has closed the connection on you for unknown reasons.
BitMEX WebSocket socket (15) | Socket gracefully closed by remote side. | 2018-08-12 22:23:58 BitMEX WebSocket | WebSocket received OpCode Close. Received status code: 0 | 2018-08-12 22:23:58 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-08-12 20:52:20] |
| User683734 - Posts: 3 |
|
Thank you for your reply I contacted BitMEX and hope I get a response from them. I followed the instructions on their site https://www.bitmex.com/app/dtcIntegration and I don't have a proxy so i can't imagine why i'd get hung up. Hopefully I can solve this because I really want to use Sierra. Date Time Of Last Edit: 2018-08-12 20:56:24
|
| [2018-08-13 17:56:27] |
| BitMEX_Sam - Posts: 7 |
|
Hi, The logs indicate you are connecting to testnet.bitmex.com. Did you set up your key on Testnet or on the live site? If your key is on the live site, please ensure you are choosing the correct connector name in Sierra Chart. |
| [2018-08-13 18:07:03] |
| |
|
In Sierra Chart, the server is controlled through Global Settings >> Data/Trade Service Settings >> Service Setting >> Server.
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: 2018-08-13 18:07:21
|
| [2018-08-13 19:02:44] |
| User683734 - Posts: 3 |
|
Hello, thank you both for assistance. Apparently i was using testnet, but i was following the instructions on the main bitmex site: https://www.bitmex.com/app/dtcIntegration I think you should update that screenshot because it points to testnet when the settings are from the live server. (bitmex.com) Basically both of your pages (bitmex and testnet.bitmex) for DTC (Sierra Chart) Integration show the same screenshot and server setting https://www.bitmex.com/img/sierra-chart-dt-settings.png Everything is working fine now, i was able to use both bitmex and testnet.bitmex api with Sierra integration Date Time Of Last Edit: 2018-08-13 20:09:38
|
| [2018-08-13 19:09:31] |
| BitMEX_Sam - Posts: 7 |
|
Good point, thanks for the note on that.
|
| [2018-08-13 20:23:12] |
| |
|
Okay we will update the image since the Testnet server is less commonly used.
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: