Hello - I have a deployment that uses IBC to manage two IB Gateway instances hosted on the same headless Linux machine but with seperate gatewaystart.sh and config.ini files. These gateways are connected using IB credentials and not the FIX CITC credentials and are read-only gateways used for retrieving info about the accounts.

In the past, I would handle basic configuration using a separate config.ini for each instance containing the login info, API port to listen on, etc. I would then typically spin up the gateway using IBC and then use a program like xterm to set the permitted external IPs directly using the gateway's user interface. However, when I try this using the newest version of IBCAlpha/the latest stable IB Gateway, if I click on the "Create" button next to the list of Trusted IPs, IBC appears to be automatically closing the resulting dialogue box by clicking OK before I have the ability to add a new IP.
I see that a new option has been added in the config.ini file called 'TrustedTwsApiClientIPs', but this appears to only be used if the Gateway is launched using FIX CITC.

I was able to workaround this by sourcing all our connections from localhost, but I wanted to check on what the intended way to set the permitted external IPs is if running the Gateway using IBC/a standard IB login. I went through the details for config.ini and did not see any options to prevent IBC from closing the Trusted IP address dialogue or to have IBC manage populating this login itself.

I have included the full logfile below, including an attempt to open the Create IP dialogue box that is automatically closed by IBC clicking OK.

Full logfile:

IB_connection_log.txt

Thank you!
Carter