Re: does IB block API connections when there have been too many missed authentication attempts?
|
Ok, I think you¡¯re confirming what I¡¯ve observed, ie that merely setting TrustedIPs in jts.ini is not enough to allow remote API connections, but ¡®Allow connections from localhost only¡¯ also has to be cleared. ? What I¡¯m aiming for is a way of establishing this configuration without any user intervention. I think what I proposed in my previous post should do the trick, so I intend to implement that some time soon. ? By the way, you say that your config.ini has settings stored on the server, but as I said yesterday there is no point in this. For Gateway, IBC completely ignores that setting, since Gateway doesn¡¯t offer that functionality. ? Richard ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Bart D via groups.io
Sent: Monday, October 23, 2023 11:47 PM
To: [email protected]; Richard L King via groups.io <rlking@...>
Subject: Re: [ibc] does IB block API connections when there have been too many missed authentication attempts?? "Can you try with a fresh instance of Gateway (ie no prior configuration except the jts.ini) and see if it still works? I don¡¯t see how it possibly can from what I¡¯m observing, so I suspect that yours is working because at some point you¡¯ve cleared the ¡®Allow connections from localhost only¡¯ checkbox."
I repeatedly start dockerized IBGW+IBC (basically a fresh install from the docker image) and it always works now without manual UI intervention. But yes I unchecked that checkbox in the IBGW UI in the past. My config is that settings are stored on server in config.ini, and both 127.0.0.1 and the fixed container IP address as trusted IPs in jts.ini.
|
