![deluge client connecting to a remote instance deluge client connecting to a remote instance](https://www.zohowebstatic.com/sites/default/files/deluge/custom-connection_summary.png)
- #DELUGE CLIENT CONNECTING TO A REMOTE INSTANCE FREE#
- #DELUGE CLIENT CONNECTING TO A REMOTE INSTANCE WINDOWS#
![deluge client connecting to a remote instance deluge client connecting to a remote instance](https://i2.wp.com/image.slidesharecdn.com/exampleforthevpnconfigurationofcisco-140502040348-phpapp01/95/example-for-the-vpn-configuration-of-cisco-1-638.jpg)
#DELUGE CLIENT CONNECTING TO A REMOTE INSTANCE FREE#
So maybe it's possible that the telnet connection you mentioned was still in place while you were trying to connect from your app? Then upgrading to 10.11 would have involved restarting, and that would free things up. The same thing applies if you're trying to step your way through the connection sequence with a debugger: until you get to the end of the sequence or you quit, no further API connections will succeed. As soon as the initial connection is released, the new connection is processed. So for example if you telnet to TWS/Gateway and just leave that connection up, you won't be able to make any further API connections: the TCP connection will succeed, and the initial handshake message (the one beginning "API") can be sent, and TWS/Gateway will receive it, but until that initial connection is released nothing more happens. One possible cause is this: if you connect to TWS/Gateway at the TCP/IP level, but you don't complete the API connection sequence, TWS/Gateway won't accept any further API connections until either you disconnect the original connection or you complete the API connection sequence. I was using 10.10 all the time before 10.11 came out with no problems. I very much doubt that this was really a problem with 10.10 that is fixed in 10.11. 19:39:14,126|DEBUG |decoder.py|no fields ***************** Nothing comes in TWS logs at time of connection, no API logs being created. 19:39:14,126|DEBUG |connection.py|socket timeout from recvMsg (, timeout('timed out'), ) 19:39:13,124|DEBUG |connection.py|socket timeout from recvMsg (, timeout('timed out'), ) Below API client logs also indicate that, it just never gets a response back to API version handshake message.
![deluge client connecting to a remote instance deluge client connecting to a remote instance](https://i.imgur.com/sPHGddj.png)
Actually connection to this remote TWS works at initial TCP handshake level.
#DELUGE CLIENT CONNECTING TO A REMOTE INSTANCE WINDOWS#
AWS security group, windows firewall settings are all correct. TWS) side or API client, most likely server. I have an API client which is able to connect to TWS on my localhost but not able to connect to this remote TWS instance. It's deployed on a Windows server 2019 on an AWS EC2 instance. TWS version being used is 10.11, latest stable version as of now.