FYI, I’m the developer of IBC, so yes, I’m quite knowledgeable about it…

?

Answers to your questions:

?

1. You need to study the User Guide! The very first page mentions Auto-Restart. Also read the section on Second Factor Authentication.
2. If you run Gateway without using IBC, you only get the alert on your phone once: if you don’t acknowledge it within 3 minutes, login fails and you have to interact directly with Gateway to login again: but IBC does that for you.
3. Running it on a cloud server is really no different from running it on your own computer, especially if it’s a Windows server, except for the following:

• For Windows:

1. You’ll need to enable Remote Desktop if you want to be able to interact with the GUI
2. You’ll need to set up a VPN tunnel to give you secure access to the GUI and the API port. I recommend WireGuard, which I use myself to access my home systems when I’m away from home.

?

• For Linux:

1. You’ll need to install a virtual frame buffer like XVFB, or something like VNC server, to enable you to access the GUI (using a VNC client)
2. You can use an SSH tunnel to secure things.
3. You might find this document helpful: It’s quite old now, and relates more to TWS than Gateway, but it contains a mass of useful information if you’re not a Linux expert

?

Richard

?

?