Support Board
Date/Time: Fri, 31 Jan 2025 19:52:05 +0000
Post From: Can SC bypass localhost traffic (e.g. TWS connection) from SOCKS 5 proxy?
| [2019-05-14 15:04:20] |
| User550780 - Posts: 8 |
|
SC proxies all network traffic (including localhost) when it is on SOCKS 5 proxy mode (see attached message log). This behavior breaks any connection to other local DTS service, e.g. an instance IB TWS running on the same computer as SC. I appreciate a quick yay or nay from SC Engineering & Support to confirm if there is a way for SC (like many other apps) to bypass localhost or certain private IPs when it is on SOCKS 5 proxy mode. Thank you. From a paid direct SC customer :) Interactive Brokers | Connecting to 127.0.0.1:7496 | 2019-05-14 10:07:49 Socket (1) | Creating socket. | 2019-05-14 10:07:49 Socket (1) | Connecting to IP: 127.0.0.1. | 2019-05-14 10:07:49 Socket (1) | Socks5 sending version and method | 2019-05-14 10:07:49 Socket (1) | Socks5 sending connection instructions | 2019-05-14 10:07:49 Socket (1) | Socks5 connected | 2019-05-14 10:07:49 Socket (1) | Socket gracefully closed by remote side. | 2019-05-14 10:07:49 Interactive Brokers | Sending API sign: API | 2019-05-14 10:07:49 Interactive Brokers | Sending client version: v100..136 +PACEAPI. Waiting for acceptance. | 2019-05-14 10:07:49 Interactive Brokers | Failed to connect to the data and trade server. | 2019-05-14 10:07:49 * Note: Is the Interactive Brokers TWS software running and is it enabled for socket clients? | 2019-05-14 10:07:49 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2019-05-14 10:07:49 Select 'File >> Disconnect' to prevent further connection attempts. | 2019-05-14 10:07:49 Socket (1) | Write in progress. Shutdown being delayed. | 2019-05-14 10:07:49 Socket (1) | Write has completed. Shutdown being performed. | 2019-05-14 10:07:49 Socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-05-14 10:07:49 Socket (1) | Closed. | 2019-05-14 10:07:49 Interactive Brokers | Disconnected. | 2019-05-14 10:07:49 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-05-14 10:07:49 File >> Disconnect selected. | 2019-05-14 10:07:52 Interactive Brokers | Disconnected. | 2019-05-14 10:07:52 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Creating socket. Using TLS 1.2. | 2019-05-14 10:10:01 The message log has been sent to support. | 2019-05-14 10:10:01 * HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Connecting to IP: 127.0.0.1. | 2019-05-14 10:10:01 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Socks5 sending version and method | 2019-05-14 10:10:01 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Socks5 sending connection instructions | 2019-05-14 10:10:01 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Socks5 connected | 2019-05-14 10:10:01 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2019-05-14 10:10:02 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-05-14 10:10:02 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Closed. | 2019-05-14 10:10:02 Sending of the Message Log is completed. The response was saved to T:\SierraChart-TWS\Data\MessageLogAnalysis.htm | 2019-05-14 10:10:02 |