Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 05 May 2024 16:58:48 +0000
Cannot Connect to VPS using DTC
View Count: 1989
| [2018-03-19 04:23:19] |
| Highlydubious - Posts: 22 |
|
Hi I have been trying for days every setting to connect to my SC instance on a VPS using DTC. Here are the logs. I've tried with both Rithmic and CQG. I have asked my VPS to turn on port forwarding on 11099 and 11098. I also turned off firewalls on both local and VPS to test. Can you see anything that I am doing incorrectly in this? DTC - Sub Instance | Connecting to the server 208.78.38.30. Port 4541 | 2018-03-18 21:13:48 DTC Client socket (618) | Creating socket. Using TLS 1.2. | 2018-03-18 21:13:48 DTC Client socket (618) | Connecting to IP: 208.78.38.30. | 2018-03-18 21:13:48 DTC - Sub Instance | Connected to server. | 2018-03-18 21:13:48 DTC - Sub Instance | Starting socket receive thread. | 2018-03-18 21:13:48 DTC - Sub Instance | Sending encoding request to server: Binary VLS | 2018-03-18 21:13:48 DTC - Sub Instance | Did not receive Encoding Response from server. Disconnecting. | 2018-03-18 21:14:08 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2018-03-18 21:14:08 Select 'File >> Disconnect' to prevent further connection attempts. | 2018-03-18 21:14:08 DTC Client socket (618) | Initiating close of socket by core. | 2018-03-18 21:14:08 DTC - Sub Instance | Disconnected. | 2018-03-18 21:14:08 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2018-03-18 21:14:08 DTC Client socket (618) | Shutdown started. Waiting for graceful close. | 2018-03-18 21:14:08 DTC - Sub Instance | Connecting to the server 208.78.38.30. Port 4541 | 2018-03-18 21:14:11 DTC Client socket (620) | Creating socket. Using TLS 1.2. | 2018-03-18 21:14:11 DTC Client socket (620) | Connecting to IP: 208.78.38.30. | 2018-03-18 21:14:11 DTC - Sub Instance | Connected to server. | 2018-03-18 21:14:11 DTC - Sub Instance | Starting socket receive thread. | 2018-03-18 21:14:11 DTC - Sub Instance | Sending encoding request to server: Binary VLS | 2018-03-18 21:14:11 File >> Disconnect selected. | 2018-03-18 21:14:17 DTC Client socket (620) | Initiating close of socket by core. | 2018-03-18 21:14:17 DTC Client socket (620) | Shutdown started. Waiting for graceful close. | 2018-03-18 21:14:17 DTC - Sub Instance | Disconnected. | 2018-03-18 21:14:17 DTC Client socket (618) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2018-03-18 21:14:18 DTC Client socket (618) | Socket gracefully closed by remote side. | 2018-03-18 21:14:18 DTC Client socket (618) | Closed. | 2018-03-18 21:14:18 DTC Client socket (617) | Timed out waiting for shutdown. Performing an immediate socket close. | 2018-03-18 21:14:38 DTC Client socket (617) | Closed. | 2018-03-18 21:14:38 DTC Client socket (617) | Socket gracefully closed by remote side. | 2018-03-18 21:14:38 DTC Client socket (617) | Deleting network socket now after delay. | 2018-03-18 21:15:08 DTC Client socket (620) | Timed out waiting for shutdown. Performing an immediate socket close. | 2018-03-18 21:15:38 DTC Client socket (620) | Closed. | 2018-03-18 21:15:38 DTC Client socket (620) | Socket gracefully closed by remote side. | 2018-03-18 21:15:38 I uploaded image as file because i am trying to show a screenshot and SC image upload will only capture the chart not the window pane i am trying to show Thank you in advance with any help, |
 2018-03-18_20-49-18.png / V - Attached On 2018-03-19 04:19:44 UTC - Size: 410.78 KB - 309 views 2018-03-18_20-50-18.png / V - Attached On 2018-03-19 04:20:10 UTC - Size: 635.43 KB - 229 views Attachment Deleted. |
| [2018-03-19 04:47:56] |
| |
|
Looks like some kind of communication problem. However: The TLS Historical Data Port needs to be set to 0 or a different port number. Cannot be the same as the other Historical Data Port. In the sub instance you need to specify your Sierra Chart username and password. Or enable: Use Sierra Chart Instance Username and Password Try not using TLS on both sides. 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-03-19 04:49:09
|
| [2018-03-19 16:59:05] |
| Highlydubious - Posts: 22 |
|
I changed the TLS Historical Data port to 0. I've also toggled between all options with Sierra Chart Username and password. I turned off TLS. I also made my home PC the server instance instead of VPS. Tried to connect with Laptop SC instance and still does not work for both VPS or PC as server. It seems this issue is not unique to the VPS because it still fails with my PC. Also it is not unique to the datafeed because it fails with both Rithmic and CQG. |
| [2018-03-19 20:38:44] |
| |
|
We tested this from our side and there is no problem. There still must be some kind of connectivity issue between those systems. Below are the logs from our side for the test: DTC Protocol server | Incoming connection from 127.0.0.1. | 2018-03-19 16:36:57
DTC client #3. 127.0.0.1 | Waiting for TLS negotiation from client. | 2018-03-19 16:36:57 DTCServer (17) | Creating socket. Using TLS 1.2. | 2018-03-19 16:36:57 DTCServer (17) | Receive buffer size: 32768 | 2018-03-19 16:36:57 DTCServer (17) | Send buffer size: 131072 | 2018-03-19 16:36:57 DTC client #3. 127.0.0.1 | Set DTC encoding to Binary VLS | 2018-03-19 16:36:57 DTC client #3. 127.0.0.1 | Requested heartbeat interval: 20 | 2018-03-19 16:36:57 DTC client #3. Sierra Chart. 127.0.0.1 | Received logon request. | 2018-03-19 16:36:57 DTC client #3. Sierra Chart. 127.0.0.1 | Sent successful Logon response message to client. Username: **. Result text: Connected to SC DTC Protocol server. Service=dtn | 2018-03-19 16:36:57 Client log: DTC - Sub Instance | Connecting to the server 127.0.0.1. Port 11094 | 2018-03-19 20:36:57 DTC Client socket (4) | Creating socket. Using TLS 1.2. | 2018-03-19 20:36:57 DTC Client socket (4) | Receive buffer size: 262144 | 2018-03-19 20:36:57 DTC Client socket (4) | Send buffer size: 0 | 2018-03-19 20:36:57 DTC Client socket (4) | Connecting to IP: 127.0.0.1. | 2018-03-19 20:36:57 DTC - Sub Instance | Connected to server. | 2018-03-19 20:36:57 DTC - Sub Instance | Starting socket receive thread. | 2018-03-19 20:36:57 DTC - Sub Instance | Sending encoding request to server: Binary VLS | 2018-03-19 20:36:57 DTC - Sub Instance | Setting DTC encoding to Binary VLS | 2018-03-19 20:36:57 DTC - Sub Instance | Sending logon request message. | 2018-03-19 20:36:57 DTC - Sub Instance | Received logon response. | 2018-03-19 20:36:57 DTC - Sub Instance | Server Name: SC DTC Server. | 2018-03-19 20:36:57 DTC - Sub Instance | Server protocol version: 8. Client protocol version: 8 | 2018-03-19 20:36:57 DTC - Sub Instance | Successfully connected. Connected to SC DTC Protocol server. Service=dtn. | 2018-03-19 20:36:57 DTC - Sub Instance | Trading is supported. | 2018-03-19 20:36:57 DTC - Sub Instance | Order cancel and replace is supported. | 2018-03-19 20:36:57 DTC - Sub Instance | OCO Orders supported. | 2018-03-19 20:36:57 DTC - Sub Instance | Bracket Orders supported. | 2018-03-19 20:36:57 DTC - Sub Instance | Connected to data and trading server. | 2018-03-19 20:36:57 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-03-19 22:08:28] |
| Highlydubious - Posts: 22 |
|
I see you are using 127.0.0.1. Were you connecting to a local instance? It connects fine when I use it on the same network. I've also run netstat in CMD on VPS and it shows my ports are listening. I can't imagine what could be going on Thanks |
| [2018-03-19 23:49:24] |
| |
|
Yes the connection is local but the problem is still definitively on your side. Especially if you do not observe a problem with a local connection. Here is a remote connection: BitMEX (Testnet) | Connecting to the server bitmextrade.sierracharts.com. Port 5567 | 2018-03-19 23:48:04
DTC Client socket (25) | Creating socket. Using TLS 1.2. | 2018-03-19 23:48:04 DTC Client socket (25) | Receive buffer size: 262144 | 2018-03-19 23:48:04 DTC Client socket (25) | Send buffer size: 0 | 2018-03-19 23:48:04 DTC Client socket (25) | Connecting to IP: 78.46.66.20. | 2018-03-19 23:48:04 BitMEX (Testnet) | Connected to server. | 2018-03-19 23:48:04 BitMEX (Testnet) | Starting socket receive thread. | 2018-03-19 23:48:04 BitMEX (Testnet) | Sending encoding request to server: Binary VLS | 2018-03-19 23:48:04 BitMEX (Testnet) | Setting DTC encoding to Binary VLS | 2018-03-19 23:48:04 BitMEX (Testnet) | Sending logon request message. | 2018-03-19 23:48:04 BitMEX (Testnet) | Received logon response. | 2018-03-19 23:48:04 BitMEX (Testnet) | Server Name: SC DTC Server. | 2018-03-19 23:48:04 BitMEX (Testnet) | Server protocol version: 8. Client protocol version: 8 | 2018-03-19 23:48:04 BitMEX (Testnet) | Successfully connected. Connected to SC DTC Protocol server. Service=BitMEXTradingMaster.DTC. | 2018-03-19 23:48:04 BitMEX (Testnet) | Trading is supported. | 2018-03-19 23:48:04 BitMEX (Testnet) | Order cancel and replace is supported. | 2018-03-19 23:48:04 BitMEX (Testnet) | OCO Orders supported. | 2018-03-19 23:48:04 BitMEX (Testnet) | Bracket Orders supported. | 2018-03-19 23:48:04 BitMEX (Testnet) | Connected to data and trading server. | 2018-03-19 23:48:04 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-03-20 02:10:46] |
| |
|
Next time you test, provide us the DTC sub instance connection log like you did above. What is unusual about this: DTC - Sub Instance | Connecting to the server 208.78.38.30. Port 4541 | 2018-03-18 21:14:11
DTC Client socket (620) | Creating socket. Using TLS 1.2. | 2018-03-18 21:14:11 DTC Client socket (620) | Connecting to IP: 208.78.38.30. | 2018-03-18 21:14:11 DTC - Sub Instance | Connected to server. | 2018-03-18 21:14:11 DTC - Sub Instance | Starting socket receive thread. | 2018-03-18 21:14:11 DTC - Sub Instance | Sending encoding request to server: Binary VLS | 2018-03-18 21:14:11 Is that the connection is actually accepted but there simply is no response from the remote side to the encoding request. Make sure the server instance of Sierra Chart is not in some kind of frozen/inoperable state. That would be highly unusual though. 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-03-21 01:52:09] |
| |
|
For testing when using the DTC - Sub Instance Service in Sierra Chart use the following: Server Address: bitmextrade.sierracharts.com Server Port: 5567 Use TLS: True Provide the Sierra Chart Message Log after trying to connect. You should just get a username or password error. 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-05-18 20:46:39] |
| Highlydubious - Posts: 22 |
|
DTC - Sub Instance | Connecting to the server bitmextrade.sierracharts.com. Port 5567 | 2018-05-18 13:44:48 DTC Client socket (15) | Creating socket. Using TLS 1.2. | 2018-05-18 13:44:48 DTC Client socket (15) | Connecting to IP: 78.46.66.20. | 2018-05-18 13:44:48 DTC - Sub Instance | Connected to server. | 2018-05-18 13:44:48 DTC - Sub Instance | Starting socket receive thread. | 2018-05-18 13:44:48 DTC - Sub Instance | Sending encoding request to server: Binary VLS | 2018-05-18 13:44:48 DTC - Sub Instance | Setting DTC encoding to Binary VLS | 2018-05-18 13:44:49 DTC - Sub Instance | Sending logon request message. | 2018-05-18 13:44:49 DTC - Sub Instance | Received logon response. | 2018-05-18 13:44:49 DTC - Sub Instance | Server Name: SC DTC Server. | 2018-05-18 13:44:49 DTC - Sub Instance | Server protocol version: 8. Client protocol version: 8 | 2018-05-18 13:44:49 DTC - Sub Instance | Connection error: Username or Password is incorrect. | 2018-05-18 13:44:49 DTC Client socket (15) | Initiating close of socket by core. | 2018-05-18 13:44:49 DTC Client socket (15) | Shutdown started. Waiting for graceful close. | 2018-05-18 13:44:49 DTC - Sub Instance | Disconnected. | 2018-05-18 13:44:49 DTC Client socket (15) | Socket gracefully closed by remote side. | 2018-05-18 13:44:49 DTC Client socket (15) | Closed. | 2018-05-18 13:44:49 Hi Sorry for the delay. Here is what I see when connecting to Bitmextrade. |
| [2018-05-18 21:19:26] |
| |
|
Yes and that is what we would expect. These indicate that the server is accepting the connection and the connection is good but obviously it is denied because of an invalid username or password. DTC - Sub Instance | Server protocol version: 8. Client protocol version: 8 | 2018-05-18 13:44:49 DTC - Sub Instance | Connection error: Username or Password is incorrect. | 2018-05-18 13:44:49 This is not what is happening when your are connecting to your own server. There is some sort of connectivity problem in that case. Maybe changing the port number would help. Try using port 5567. 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-05-18 21:23:13] |
| Highlydubious - Posts: 22 |
|
I attempted login again using Rithmic and surprisingly it's actually working now. I don't believe I did anything differently except waited 2 months to re-try. Both orders and charts seem to be updating. Markets are closed now, so I will test out next week. Is there any way to make an alert in the Alerts log or Alert on a line and have it mirrored to my VPS instance? When I close my local DTC Subinstance, i lose my alerts. It would be nice to have server side (my VPS) alerts. Thank you, |
| [2018-05-19 00:21:36] |
| |
|
No, alerts do not transfer over a DTC connection. But there is the capability to save these to a file. Global Settings >> General Settings >> General 4 >> Save Alerts Log to File. 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-05-20 22:21:12] |
| Highlydubious - Posts: 22 |
|
Thank you. Where can i find the log file? Can I theoretically save the log file onto a folder on the cloud and have my VPS instance reading the same folder?
|
| [2018-05-21 16:46:35] |
| Highlydubious - Posts: 22 |
|
Hi following up. I found this post. Where does alerts file reside? I have selected save Alerts to Log file in General 4. I put some alerts in the alerts manager. Then I go into the folder 'Logs' in my SC instance and there are no new saves. Is there a different folder that these alerts logs are saved in? Do I have to shutdown SC? I did 'Save All' thinking that might get the alerts to populate the log file. Still nothing. I'm not sure what I'm doing incorrectly here. |
| [2018-05-21 21:04:42] |
| |
|
Refer to the documentation here for saving the alert log to a file: http://www.sierrachart.com/index.php?page=doc/GeneralSettings.html#SaveAlertsLogToFile The file location cannot be changed. But you can always set up a batch file script to copy that file and do what you want with it. We do not see any problems with the saving of the alerts log to a file. Make sure you are running the current version of Sierra Chart. 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-05-21 21:05:20
|
| [2018-05-21 22:09:46] |
| Highlydubious - Posts: 22 |
|
Here where i am stuck. First, what is the difference between 'Alerts Log' and 'Symbol Alerts' in the Alerts Window? I put in a 'Symbol Alert'. Then I go into the 'Logs' folder. There are no new alert log files until after an alert has been activated.
|
| [2018-05-22 04:30:23] |
| |
|
The Alerts Log is for chart, study, trading alerts and other types of alerts. And the Symbol Alerts are just for Symbol Alerts. Symbol Alerts are not saved to a file. 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-05-22 05:16:06] |
| Highlydubious - Posts: 22 |
|
Thank you. I have been now been testing out chart alerts drawn off horizontal lines. There is no log in the Alert Log until the alert has been triggered. It's there a temp file that the 'pre' alerts are stored in (that i could then sync with my VPS instance)? Is it theoretically programable for the DTC protocol to allow for something like alerts to transfer between SC instances? Or even something that could be done on SC end? I imagine Server side alerts would be a feature a lot of customers would enjoy. |
| [2018-05-22 05:30:17] |
| |
|
It's there a temp file that the 'pre' alerts are stored in (that i could then sync with my VPS instance)? No, only when there is an actual triggered alert will it be logged.Is it theoretically programable for the DTC protocol to allow for something like alerts to transfer between SC instances?
Well, it certainly would be possible but we would have to add messages for 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 |
| [2018-05-22 19:40:31] |
| Highlydubious - Posts: 22 |
|
No, only when there is an actual triggered alert will it be logged.
Does this mean that if i set a horizontal alert there would be no possible way to have the same pre alert log file saved to my VPS instance (and become a server based alert)? Can you think of anyway with the current setup that drawing an alert on a local SC instance could be saved on my VPS SC instance at the same time? Well, it certainly would be possible but we would have to add messages for this.
I think it would be a very useful feature. People wanted server side orders and now most brokers support them. Local instance to VPS alerts would almost be a DIY server side alert system. You could put the alert in knowing it's going to trigger regardless if the local SC instance loses connection. It would be a great feature. |
| [2018-05-22 20:16:39] |
| |
|
We really cannot provide any further help here.
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-06-04 21:25:21] |
| Highlydubious - Posts: 22 |
|
Where can I make a suggestion to include local to DTC server instance drawing alerts. As long as the VPS is at near 100% uptime, this would ensure alerts actually get triggered even when a local instance goes down. Sierra Chart is almost perfect, but non server-side alerts has caused me a lot of issues. I prefer SC in most ways but Tradingview, Think or Swim, and many other platforms have this functionality built in. |
| [2018-06-05 06:17:21] |
| |
|
The suggestion can be made here but refer to: Notice: Suggestions (Currently not accepting) 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-06-11 21:32:31] |
| |
|
Where can I make a suggestion to include local to DTC server instance drawing alerts. As long as the VPS is at near 100% uptime, this would ensure alerts actually get triggered even when a local instance goes down.
A case has come up where there is a need for us to pass alerts through from a server instance to the client instance so we are going to be developing the capability to pass through all alert messages in the Alerts Log over the DTC server which can then be received by the client and added to the Alerts Log on the client side. So this is coming. 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-06-11 21:33:27
|
| [2018-06-12 16:41:34] |
| Highlydubious - Posts: 22 |
|
This is great news. To confirm, does this mean I can set a horizontal line alert on my local side and have it trigger from the VPS even when my local instance is closed, loses internet, etc. Can these alerts pass in both direction client->server, server->cleint, depending on which instance the alert is set on?
|
To post a message in this thread, you need to log in with your Sierra Chart account: