Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 28 Apr 2024 05:41:52 +0000
Issue with Proxy - Sierra logs in, but can't connect to BitMEX
View Count: 1322
| [2018-09-24 07:58:16] |
| Holgy1975 - Posts: 1 |
|
Hello! I have an issue when using Sierra Chart from behind our corporate firewall and proxy. If I am at home where I have no proxy, Sierra works flawlessly, however at our office it can't connect to BitMEX. Our corporate firewall drops all TCP connections that do not pass through the proxy server. Proxy speaks TLS 1.2 (I've checked it by inspecting "Server Hello" message sent from the server). When I set up proxy address in Sierra it verifies my account, logs in, tries to open up a connection to BitMEX through the proxy, but fails: Reading Internal Order ID file. | 2018-09-24 10:50:08 Reading Trade Orders file. | 2018-09-24 10:50:08 Reading Trade Positions and Account Balance file. | 2018-09-24 10:50:08 Listening on UDP port 22904. | 2018-09-24 10:50:08 Software version: 1809 64-bit | 2018-09-24 10:50:08 Usage end date: 2018-10-07 | 2018-09-24 10:50:08 Enabled for: Advanced Features. | 2018-09-24 10:50:08 Enabled for: Advanced Features 2. | 2018-09-24 10:50:08 Enabled for: Sierra Chart Historical Data Service. | 2018-09-24 10:50:08 Allow Support for Sierra Chart Data Feeds is enabled. | 2018-09-24 10:50:08 Current selected Data/Trading service: BitMEX Trading Direct | 2018-09-24 10:50:08 Chart Update Interval: 500 | 2018-09-24 10:50:08 Time Zone: +03:00:00 (EET+02EEST+01,M3.5.0/03:00,M10.5.0/04:00) | 2018-09-24 10:50:08 2018-09-24 10:50:08 Local computer time | 2018-09-24 10:50:08 2018-09-24 07:50:08 Local computer time in UTC | 2018-09-24 10:50:08 2018-09-24 10:50:08 Local computer time in SC Time Zone | 2018-09-24 10:50:08 Program path: C:\Portable\SierraChart\ | 2018-09-24 10:50:08 Data Files path: C:\Portable\SierraChart\Data\ | 2018-09-24 10:50:08 OS Version Number: 10.0 | 2018-09-24 10:50:08 Locale Setting: C | 2018-09-24 10:50:08 Checking for new symbol settings for service code bitmex.exchange.trading | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (4) | Creating socket. Using TLS 1.2. | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (4) | Connecting to IP: 16.46.41.11. | 2018-09-24 10:50:08 Subscribing to market data for symbol XBTZ18-BMEX for trade position profit/loss. | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (2) | Encryption stream error encountered when processing received data. Failed to read incoming decrypted data from the incoming binary I/O stream. error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (2) | Received socket Close event. | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (2) | Signaling to core to close socket | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (2) | Shutdown started. Waiting for graceful close. | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (4) | Encryption stream error encountered when processing received data. Failed to read incoming decrypted data from the incoming binary I/O stream. error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (4) | Received socket Close event. | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (4) | Signaling to core to close socket | 2018-09-24 10:50:08 HTTP request 1 for symbol settings MD5 for bitmex.exchange.trading finished. Connection for request failed. Reason: HTTP server closed the connection for unknown reason after sending initial request. | 2018-09-24 10:50:08 HTTPS web-proxy.sdc.hpecorp.net:8080 (4) | Shutdown started. Waiting for graceful close. | 2018-09-24 10:50:08 Then it tries to contact BitMEX directly, but of course it fails because of our FW: BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2018-09-24 10:50:12 BitMEX WebSocket | Connecting to WebSocket server. | 2018-09-24 10:50:12 BitMEX WebSocket socket (5) | Creating socket. Using TLS 1.2. | 2018-09-24 10:50:12 BitMEX WebSocket socket (5) | Connecting to IP: 54.171.8.37. | 2018-09-24 10:50:12 BitMEX WebSocket socket (5) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2018-09-24 10:50:33 * BitMEX WebSocket socket (5) | Signaling to core to close socket | 2018-09-24 10:50:33 BitMEX WebSocket | WebSocket closed. | 2018-09-24 10:50:33 BitMEX Trading Direct | WebSocket closed. | 2018-09-24 10:50:33 BitMEX WebSocket socket (5) | Closed. | 2018-09-24 10:50:33 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2018-09-24 10:50:33 Select 'File >> Disconnect' to prevent further connection attempts. | 2018-09-24 10:50:33 BitMEX Trading Direct | Disconnected. | 2018-09-24 10:50:33 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2018-09-24 10:50:33 BitMEX Trading Direct | Connecting to URI www.bitmex.com/realtime/WebSocket | 2018-09-24 10:50:36 BitMEX WebSocket | Connecting to WebSocket server. | 2018-09-24 10:50:36 BitMEX WebSocket socket (6) | Creating socket. Using TLS 1.2. | 2018-09-24 10:50:36 BitMEX WebSocket socket (6) | Connecting to IP: 54.171.8.37. | 2018-09-24 10:50:36 Obviously, the issue is "SSL3_GET_RECORD:wrong version number" error, but I am 100% our proxy speaks TLS 1.2. I have attached an example of browser's connection through the proxy, so you can check "Server Hello" TLVs. Is there anything I can do to make Sierra Chart to work through the proxy server? Best regards, Holger |
 browser_proxy_connection.pcapng - Attached On 2018-09-24 07:55:38 UTC - Size: 4.24 KB - 234 views  sierra_screenshot.png / V - Attached On 2018-09-24 07:57:43 UTC - Size: 82.62 KB - 257 views |
| [2018-09-24 18:51:23] |
| |
|
First thing is we need to be 100% certain that you can log into Sierra Chart without a problem. The way for us to confirm that is for you to perform a Forced Login procedure: Sierra Chart - Software Login Instructions: Forced Login HTTPS web-proxy.sdc.hpecorp.net:8080 (4) | Encryption stream error encountered when processing received data. Failed to read incoming decrypted data from the incoming binary I/O stream. error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number | 2018-09-24 10:50:08
In general this does relate to the TLS version being used. Maybe you could try connecting to BitMex through a publicly available proxy server, from an unrestricted location, and find out if you have the same problem.
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: