Support Board
Date/Time: Mon, 03 Mar 2025 21:55:21 +0000
Bitmex
View Count: 1188
| [2021-10-22 20:48:47] |
| User471027 - Posts: 19 |
|
Hello, thanks for following up. I was trying to connect Bitmex with Sierra Chart and have copied their set up suggestion; see screenshot attached. However, Sierra Chart still did not connect properly. I also followed the steps you suggested via https://www.sierrachart.com/index.php?page=doc/BitMEX_Trading.php#BitmexConnectionProblems A few hours was waited before trying to connect again and also a new API key was created. Still the same connection issues. See also the message log: Software version: 2320 64-bit | 2021-10-22 14:57:02.299 Primary Thread ID: 14200 | 2021-10-22 14:57:02.299 Usage end date: 2022-04-28 | 2021-10-22 14:57:02.300 Enabled for: Advanced Features 2. | 2021-10-22 14:57:02.300 Enabled for: Sierra Chart Historical Data Service. | 2021-10-22 14:57:02.300 Enabled for: Denali Real-Time Exchange Data Feed. | 2021-10-22 14:57:02.300 Enabled for: Delayed Denali Exchange Data Feed. | 2021-10-22 14:57:02.300 Enabled for exchange2: fairx_exchange.data | 2021-10-22 14:57:02.300 Allow Support for Sierra Chart Data Feeds is enabled. | 2021-10-22 14:57:02.300 Current selected Data/Trading service: BitMEX Trading Direct | 2021-10-22 14:57:02.300 Custom symbol settings values: enabled | 2021-10-22 14:57:02.300 Chart Update Interval: 500 | 2021-10-22 14:57:02.300 Intraday Data Storage Time Unit: 1 | 2021-10-22 14:57:02.300 Time Zone: +00:00:00 (UTC+00) | 2021-10-22 14:57:02.300 2021-10-22 14:57:02 Local computer time in UTC | 2021-10-22 14:57:02.300 2021-10-22 14:57:02 Local computer time in SC Time Zone | 2021-10-22 14:57:02.300 2021-10-22 14:51:48 Server time in UTC | 2021-10-22 14:57:02.300 Local computer UTC time and Server UTC time difference: 2 seconds. | 2021-10-22 14:57:02.300 Program path: C:\SierraChartCrypto\ | 2021-10-22 14:57:02.300 Data Files path: C:\SierraChartCrypto\Data\ | 2021-10-22 14:57:02.300 OS Version Number: 10.0 | 2021-10-22 14:57:02.300 Locale Setting: C | 2021-10-22 14:57:02.300 DLLs: UserContributedStudies_64.dll | 2021-10-22 14:57:02.300 Allowed protected custom studies: | 2021-10-22 14:57:02.300 BitMEX Trading Direct | Opening WebSocket. | 2021-10-22 14:57:02.323 BitMEX Trading Direct | Sending WebSocket handshake. | 2021-10-22 14:57:02.323 BitMEX Trading Direct | Server header | HTTP/1.1 429 Too Many Requests | 2021-10-22 14:57:02.421 BitMEX Trading Direct | Unexpected header. Handshake acknowledgment: HTTP/1.1 429 Too Many Requests. Disconnecting | 2021-10-22 14:57:02.421 BitMEX Trading Direct | WebSocket closed. | 2021-10-22 14:57:02.421 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2021-10-22 14:57:02.421 Select 'File >> Disconnect' to prevent further connection attempts. | 2021-10-22 14:57:02.421 BitMEX Trading Direct socket (1) | CloseSocket call. | 2021-10-22 14:57:02.441 BitMEX Trading Direct | WebSocket closed. | 2021-10-22 14:57:02.441 BitMEX Trading Direct | WebSocket closed. | 2021-10-22 14:57:02.441 BitMEX Trading Direct | Disconnected. | 2021-10-22 14:57:02.441 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2021-10-22 14:57:02.441 BitMEX Trading Direct socket (1) | Shutdown started. Waiting for graceful close. | 2021-10-22 14:57:02.441 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2021-10-22 14:57:02.470 BitMEX Trading Direct socket (1) | Closed. | 2021-10-22 14:57:02.470 Bitmex states "If you have issues, please notify Sierra Chart directly. Our development teams are working closely together, and if the problem is on BitMEX’s end, they will contact us." Any ideas how to proceed here? Thank you and have a good weekend! Kind regards, https://www.sierrachart.com/Download.php?Folder=TicketingSystem&download=56060 |
| [2021-10-22 21:02:01] |
| John - SC Support - Posts: 38341 |
|
The problem you are having is described here: https://www.sierrachart.com/index.php?page=doc/BitMEX_Trading.php#BitmexConnectionProblems As noted in that documentation, we do not know how long you need to wait before they will let you connect again. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2021-10-23 19:13:16] |
| User471027 - Posts: 19 |
|
Yes.. I saw that page as mentioned in my message. I also followed the steps you suggested via https://www.sierrachart.com/index.php?page=doc/BitMEX_Trading.php#BitmexConnectionProblems
A few hours was waited before trying to connect again and also a new API key was created. Still the same connection issues. I waited a few hours yesterday and tried again today - more than 24 hours later. Are you suggesting to get in touch with Bitmex then? Kind regards |
| [2021-10-24 05:34:21] |
| |
|
Yes we have no control over 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 |
| [2021-11-14 13:16:20] |
| User471027 - Posts: 19 |
|
I was in an exchange with Bitmex the past days. They investigated on their side and tried to fix it. Yesterday, I received the below message: My apologies for the delay.
The Sierra Chart Engineering team confirmed that they either want or already have updated the connection address. BitMex Data Feed This should resolve the issue. Unfortunately, we're not aware of a timeframe when this will be fixed on their end. Regards, So, I followed that link and the mentioned instructions. However, those instructions do only allow simulation trading. There is no direct connection to Bitmex. There is also a link (https://blog.bitmex.com/site_announcement/reminder-change-of-websocket-endpoint-by-1-november/) in that thread stating they will do an update November 1st but that is already two weeks ago. Once again I contacted the Bitmex support receiving the below message: So you weren't asked to enter your API key and API Secret? Please try contacting sierra chart's support to ask what the workaround is for integration.
Regards, Not sure whether I understood something wrong here but can you please shed some light on that? I would like to trade a live account with Bitmex. Thank you. |
| [2021-11-15 04:24:34] |
| Sierra_Chart Engineering - Posts: 18631 |
|
Update Sierra Chart to the latest prerelease: Software Download: Fast Update We have updated the BitMex connection address. 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: 2021-11-15 04:25:30
|
| [2021-11-15 10:29:43] |
| User471027 - Posts: 19 |
|
Done but still the same problem - the platform does not connect. See log below: Software version: 2328 64-bit | 2021-11-15 10:22:46.091 Primary Thread ID: 4516 | 2021-11-15 10:22:46.091 Usage end date: 2022-04-28 | 2021-11-15 10:22:46.091 Enabled for: Advanced Features 2. | 2021-11-15 10:22:46.091 Enabled for: Sierra Chart Historical Data Service. | 2021-11-15 10:22:46.091 Enabled for: Denali Real-Time Exchange Data Feed. | 2021-11-15 10:22:46.091 Enabled for: Delayed Denali Exchange Data Feed. | 2021-11-15 10:22:46.091 Enabled for exchange2: CME (Trading Account Required) | 2021-11-15 10:22:46.091 Enabled for exchange2: CBOT (Trading Account Required) | 2021-11-15 10:22:46.091 Enabled for exchange2: COMEX (Trading Account Required) | 2021-11-15 10:22:46.091 Enabled for exchange2: NYMEX (Trading Account Required) | 2021-11-15 10:22:46.091 Enabled for exchange2: fairx_exchange.data | 2021-11-15 10:22:46.091 Allow Support for Sierra Chart Data Feeds is enabled. | 2021-11-15 10:22:46.091 Current selected Data/Trading service: BitMEX Trading Direct | 2021-11-15 10:22:46.091 Custom symbol settings values: enabled | 2021-11-15 10:22:46.091 Chart Update Interval: 500 | 2021-11-15 10:22:46.091 Intraday Data Storage Time Unit: 1 | 2021-11-15 10:22:46.091 Time Zone: +00:00:00 (UTC+00) | 2021-11-15 10:22:46.091 2021-11-15 10:22:46 Local computer time in UTC | 2021-11-15 10:22:46.091 2021-11-15 10:22:46 Local computer time in SC Time Zone | 2021-11-15 10:22:46.091 2021-11-15 10:19:46 Server time in UTC | 2021-11-15 10:22:46.091 Local computer UTC time and Server UTC time difference: 2 seconds. | 2021-11-15 10:22:46.091 Program path: C:\SierraChart Crypto\ | 2021-11-15 10:22:46.091 Data Files path: C:\SierraChart Crypto\Data\ | 2021-11-15 10:22:46.091 OS Version Number: 10.0 | 2021-11-15 10:22:46.091 Locale Setting: C | 2021-11-15 10:22:46.091 DLLs: UserContributedStudies_64.dll | 2021-11-15 10:22:46.091 Allowed protected custom studies: | 2021-11-15 10:22:46.091 BitMEX Trading Direct | Connecting to URI ws.bitmex.com/realtime | 2021-11-15 10:22:48.622 BitMEX Trading Direct | Connecting to WebSocket server ws.bitmex.com:443 | 2021-11-15 10:22:48.622 BitMEX Trading Direct socket (2) | Creating socket. Using TLS 1.2. | 2021-11-15 10:22:48.623 BitMEX Trading Direct socket (2) | New receive buffer size: 5242880 | 2021-11-15 10:22:48.623 BitMEX Trading Direct socket (2) | Connecting to IP: 172.65.213.179. | 2021-11-15 10:22:48.623 BitMEX Trading Direct | Opening WebSocket. | 2021-11-15 10:22:48.642 BitMEX Trading Direct | Sending WebSocket handshake. | 2021-11-15 10:22:48.642 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2021-11-15 10:22:48.755 BitMEX Trading Direct | Server header | upgrade: websocket | 2021-11-15 10:22:48.755 BitMEX Trading Direct | Server header | Connection: Upgrade | 2021-11-15 10:22:48.755 BitMEX Trading Direct | Server header | sec-websocket-accept: +zRLKyku6IeZQLs2Yu9iTD2/Z34= | 2021-11-15 10:22:48.755 BitMEX Trading Direct | Server header | sec-websocket-version: 13 | 2021-11-15 10:22:48.755 BitMEX Trading Direct | Server header | websocket-server: uWebSockets | 2021-11-15 10:22:48.755 BitMEX Trading Direct | Server header | | 2021-11-15 10:22:48.756 BitMEX Trading Direct | Web socket state is now open. | 2021-11-15 10:22:48.756 BitMEX Trading Direct | Connected to server complete. | 2021-11-15 10:22:48.756 Triggering next historical data download in queue. | 2021-11-15 10:22:48.756 Triggering next historical data download in queue. | 2021-11-15 10:22:48.756 Triggering next historical data download in queue. | 2021-11-15 10:22:48.756 Triggering next historical data download in queue. | 2021-11-15 10:22:48.757 No download requests in the queue to start downloads for. | 2021-11-15 10:22:48.757 No download requests in the queue to start downloads for. | 2021-11-15 10:22:48.757 No download requests in the queue to start downloads for. | 2021-11-15 10:22:48.757 No download requests in the queue to start downloads for. | 2021-11-15 10:22:48.757 BitMEX Trading Direct | WebSocket received OpCode Close. Received status code: 0 | 2021-11-15 10:22:48.804 BitMEX Trading Direct | WebSocket closed. | 2021-11-15 10:22:48.804 Connection to the external service has been lost. | 2021-11-15 10:22:48.804 BitMEX Trading Direct socket (2) | CloseSocket call. | 2021-11-15 10:22:48.822 BitMEX Trading Direct | WebSocket closed. | 2021-11-15 10:22:48.822 BitMEX Trading Direct | WebSocket closed. | 2021-11-15 10:22:48.822 BitMEX Trading Direct | Disconnected. | 2021-11-15 10:22:48.822 BitMEX Trading Direct socket (2) | Write in progress. Shutdown being delayed. PendingSize=0 | 2021-11-15 10:22:48.822 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2021-11-15 10:22:48.822 BitMEX Trading Direct socket (2) | Write has completed. Shutdown being performed. | 2021-11-15 10:22:48.874 BitMEX Trading Direct socket (2) | Shutdown started. Waiting for graceful close. | 2021-11-15 10:22:48.874 BitMEX Trading Direct socket (2) | Socket gracefully closed by remote side. | 2021-11-15 10:22:48.892 BitMEX Trading Direct socket (2) | Closed. | 2021-11-15 10:22:48.893 |
| [2021-11-15 11:51:54] |
| |
|
This is the problem in your case: BitMEX Trading Direct | WebSocket received OpCode Close. Received status code: 0 | 2021-11-15 10:22:48.804 BitMex is closing the connection for unknown reasons. We cannot help with this. We are intending to remove support for BitMex in the coming months. 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: