Error when running Docker image about thetagang HOT 5 CLOSED

Check the IBC log, which should be written out to ibc.log by default (again, defined in thetagang.toml). Common issues are the wrong credentials, bad settings, API port not enabled, wrong API port, networking issues, etc.

from thetagang.

Well that's a strange one. Have you tried using the sample config.ini from the repo? Also, check that you have gateway = true in your thetagang.toml like this.

I have no idea why TWS needs to render CSS to run the gateway, but I guess it's because nobody who works in management at IB has realized you can run a Java app without a GUI.

from thetagang.

OK there is no error now, but it doesn't look like it's doing anything but printing the config.

from thetagang.

I don't see a log file being created (/ibc/ib_insync.log), so I'm not sure there's any output

from thetagang.

If you're running it with Docker, you need to make sure the log is being written out to somewhere you can grab it, i.e., to a volume. In my case, I mount the volume at /ibc inside the container, and I changed the logfile path to /ibc/ibc.log. So my docker command looks like:

$ docker run -v ~/ibc:/ibc ...

And my thetagang.toml looks like:

[ib_insync]
logfile = '/ibc/ibc.log'

Alternatively you can jump inside the container with docker exec -it <container> /bin/bash and fetch the log that way.

from thetagang.