Support Board
Date/Time: Sat, 01 Feb 2025 10:01:09 +0000
Trial Account - Bitmex Login Failures
View Count: 1085
| [2019-07-05 23:31:44] |
| scottsen - Posts: 3 |
|
Is there some way to see the actual http request/response -- in hopes of getting more info on the error? BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2019-07-05 23:26:42.980 BitMEX Trading Direct | Connecting to WebSocket server. | 2019-07-05 23:26:42.980 BitMEX Trading Direct socket (1) | Creating socket. Using TLS 1.2. | 2019-07-05 23:26:42.980 BitMEX Trading Direct socket (1) | Connecting to IP: 54.77.89.171. | 2019-07-05 23:26:42.980 BitMEX Trading Direct | Opening WebSocket. | 2019-07-05 23:26:43.138 BitMEX Trading Direct | Sending WebSocket handshake. | 2019-07-05 23:26:43.138 BitMEX Trading Direct | Server header | HTTP/1.1 101 Switching Protocols | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | Date: Fri, 05 Jul 2019 23:26:48 GMT | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | Connection: upgrade | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | Set-Cookie: AWSALB=DNbnOhRftINH0kFWNKYKS6V6lRjz4WJCZdN8by8ADDnSLdpRzIVHPBxxaTJmC0q6hRB8DN+fVog9PtQBj082wBOZDERvkBfQljpt46Hxhx71b2xtOaqfDqDLSmdS; Expires=Fri, 12 Jul 2019 23:26:48 GMT; Path=/ | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | Upgrade: websocket | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | Sec-WebSocket-Accept: Z24UbMN2hJx26yrZXnoylxABToE= | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | Sec-WebSocket-Version: 13 | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | WebSocket-Server: uWebSockets | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | Strict-Transport-Security: max-age=31536000; includeSubDomains | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Server header | | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Web socket state is now open. | 2019-07-05 23:26:43.651 BitMEX Trading Direct | Connected to data and trading server. | 2019-07-05 23:26:43.651 BitMEX Trading Direct | WebSocket received OpCode Close. Received status code: 0 | 2019-07-05 23:26:43.838 BitMEX Trading Direct | WebSocket closed. | 2019-07-05 23:26:43.838 Connection to the external service has been lost. | 2019-07-05 23:26:43.838 BitMEX Trading Direct socket (1) | Socket gracefully closed by remote side. | 2019-07-05 23:26:43.838 BitMEX Trading Direct | Network socket for WebSocket has been closed by remote side or error. | 2019-07-05 23:26:43.839 BitMEX Trading Direct | WebSocket closed. | 2019-07-05 23:26:43.839 BitMEX Trading Direct socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-07-05 23:26:43.839 BitMEX Trading Direct socket (1) | Closed. | 2019-07-05 23:26:43.839 BitMEX Trading Direct | Disconnected. | 2019-07-05 23:26:43.859 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-07-05 23:26:43.860 |
| [2019-07-06 01:52:07] |
| |
|
We know exactly what is happening from this log. This is the problem: BitMEX Trading Direct | WebSocket received OpCode Close. Received status code: 0 | 2019-07-05 23:26:43.838 Try generating a new API key and secret: https://www.sierrachart.com/index.php?page=doc/BitMEX_Trading.php#SetupInstructions And make sure the Server setting is set correctly, either Live or Testnet. 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-07-06 08:20:36] |
| scottsen - Posts: 3 |
|
*Exactly* ? I mean, we know they closed it. But they don't give any other error information in the underlying http packets? I literally created new keys just for this purpose, don't have a test account at bitmex, and double checked Server was set to live on SC. |
| [2019-07-06 08:40:26] |
| scottsen - Posts: 3 |
|
Found it! I had a single "space" after my key. <sigh>. Past this problem! :) Thanks much.
|
To post a message in this thread, you need to log in with your Sierra Chart account: