It seems I spoke too soon when I said it looks like IB really are retiring TWS972: I ran it up last night, and it worked fine, so it's clearly not dead yet.

?

So apologies if I alarmed anyone unnecessarily. However, I do think it's always a bad idea to use old versions of TWS, because they are no longer updated by IB if bugs are found.

?

I appreciate that some are still using 972 with IBC because it enables them to keep TWS up and running as long as they want. But that is a fight you cannot win: eventually IB will stop 972 working, and what will you do then? So even if you continue to use 972 temporarily, you really must take steps to move on to a current version sooner rather than later.

?

Also mixed up in this thread is the issue of SSL: it now appears that IB are insisting on use of SSL. Fair enough, though it would have been nice to be less heavy-handed about it.

?

• If you use TWS manually, or via IBC with an accessible user interface, then just accept the SSL nag dialog and all will be well: what this actually does is to set the value UseSSL=true in the jts.ini file (if you don't know what that is, don't worry, you don't really need to know).
• If you're running IBC without an accessible GUI, then you should ensure that you always have a valid jts.ini with UseSSL=true when IBC starts. Examples of this might be:

?

• on a headless (perhaps remote) server
• in an environment where jts.ini is not preserved between sessions (eg some Docker images that don't preserve state between sessions – which I consider to be poor practice)

?

If for some reason you can't ensure a valid jts.ini, then you'll just have to wait until I update IBC to provide a workaround (hopefully in time for the start of next week). My current thinking is to enhance IBC's existing jts.ini checking to ensure that UseSSL=true is always set. This will mean you won't be able to turn SSL off, but it appears that IB won't allow this anyway so this shouldn't be an issue. Any comments on this proposal would be welcomed, either here, or the IBC User Group, or this issue on the IBC GitHub repository: .

?

Richard

?