Closed prachetasp closed 6 years ago
I probably should have read a little more through the other open issues before posting this. Looks like in #10 specially creating and copying in an ibg.xml
should allow me to disable this functionality. Is that correct?
Also for others that might come across this it seems that ibg.xml
is only written when you close IBGateway not when you click apply in the settings screens.
@coltonbh originally created this issue on IBController (https://github.com/ib-controller/ib-controller/issues/181) but copying here since I am essentially facing the same issue:
I'm trying to run the IB Gateway in a docker container (headless). One issue I'm facing is that when the gateway starts up the "Allow connections from localhost only" is selected by default, so I can only connect to the gateway if connecting from localhost, not from another docker container. I can inject "TrustedIPs" in the jts.ini file with a list of ip addresses and the gateway adds this list, but the "Allow connections from localhost only" remains selected so I still can't connect to the gateway from any other container not on the gateway's localhost.
We've circumvented this issue by using socat to fork the localhost port onto an external port that can be reached from external containers, but this has a number of undesired side effects we'd like to eliminate.
Is there a way to deselect the "Allow connections from localhost only" using the jts.ini file so the gateway can receive connections directly from other docker containers?