开云体育

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

"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

I was misguidedly thinking that storing the settings periodically would help with the ensuring the settings stored on the server are up to date, but in fact it turns out that Gateway doesn’t support

Bart, you wrote as problem description as "repeatedly starting TWS/Gateway, logging in successfully, and then restarting after a short time". In the past I have had that issue myself, without using

"are you aware that you can configure IBC to save the TWS/Gateway settings at times of your choosing? See SaveTwsSettingsAt in config.ini." It would not help when the container restarts: any update

Thanks for that. A couple of points that might be of interest: First, are you aware that you can configure IBC to save the TWS/Gateway settings at times of your choosing? See SaveTwsSettingsAt in

I found the root cause of this and it was something totally different. When you run a dockerized multi-container app, each container gets an IP address from a local gateway on the docker host that

Richard, thanks for reply and the excellent IBC. It seems you're the sole person who has made unatttended operation with IB possible! The situation was "repeatedly starting TWS/Gateway, logging in

I’m a bit unclear about the situation here. In the subject, you mention ‘too many missed authentication attempts’, but you don’t explain what you mean by this in the message. If you keep

During development of an automated trading engine, I've experienced an interesting situation: - using dockerized IB gateway+IBC I could connect from my client python software (using client ID 0) with

Chen, Brian, any progress, or questions, or further input on this? It occurs to me that perhaps you’re using ib_insync, which I believe will start TWS for you automatically (using IBC under the

Look in twsstartmacos.sh. You’ll see the setting for the LOG_PATH variable. The log files themselves have names like this: ibc-3.18.0_TWS-1025_wednesday.txt Now read the descriptive comment

Hi Richard, Thanks for pointing that out. I can see the Title "IbcTws" and if I click on About a small widow pops out. Please see the image attached. We appreciate your help and guidance immensely.

I don’t want the launcher logs, I want the IBC logs. When you run IBC a prominent banner window is displayed telling you where the IBC log is. That’s what I need. The launcher logs are written

Hi Richard, We really appreciate your help here. Your willingness to help directly with users like us is commendable. The ubuntu box has already been on 3.18.0 and I've attached the launcher logs

OK, the first thing to say is that if you are experiencing problems while using IBC, you should post here and attach the IBC logfile so that I can have a look at what’s going on. And I mean attach

@All, Chen and I have been working on this issue together prior to coming to this group for further insight and let me expound on what it seems is happening. We install TWS on both a ubuntu server

Sloppy wording on my part. "you only get a forced restart over the weekend" if you set the Gateway to auto restart

Hi Chen I don't think there's a way round that with TWS. But it can be made reasonably painless with IBC and IB Gateway. With Gateway you only get a forced restart over the weekend. I schedule my

Hi, For the last 2 years, I have kept TWS consistently and constantly running through daily scheduled and every odd unscheduled restart with the need for any human intervention. This is achieved