-
Describe the bugIf followed the documentation, and docker-compose up to run the contianer, and try to connect to it, but I got following error ib-gateway_1 | 2024-05-18 07:29:31:800 IBC: Waiting for config dialog future to complete just want to understand, is it the VNC is up and running, if I can login to the VNC UI to see what happend, I try to access 127.0.0.1:5900, there is not response on the browser the .env as below TWS_USERID= ib-gateway#TWS_SETTINGS_PATH=/home/ibgateway/Jts tws#TWS_SETTINGS_PATH=/config/tws_settings To ReproduceSteps to reproduce the behavior. Please include information related to docker, Please provide the output of ExpectedA clear and concise description of what you expected to happen. Container logsIf applicable, add the container logs VersionsPlease complete the following information:
Additional contextAdd any other context about the problem here. What have you tried and failed. My primary objective is to fix any bug on the container, ex Dockerfile, run.sh |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments
-
|
Depending on what you did on your docker-compose.yml you might be able to log into VNC. based on the Please provide the output of |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply, my docker-compose.yml file as below and yes I use the latest tag, what I don't understand is when I launched IB Gateway through GUI before, it ask me to verify through SNS message, but if you put IB Gateway, how to implement the SNS message authentication? and how do you connect to VNC? through browser? I had some VNC image before, I can connect it through the browser, but looks it failed on this one. not very sure where I am wrong in which steps. and when I run the python to test the connection to that docker container, I can see the log message as below and the connection is timeout and failed |
Beta Was this translation helpful? Give feedback.
-
|
Please provide the output of |
Beta Was this translation helpful? Give feedback.
-
|
docker compose config as below (TWS_USERID, TWS_PASSWORD I hide the values) docker images --digests as below REPOSITORY TAG DIGEST IMAGE ID CREATED SIZE |
Beta Was this translation helpful? Give feedback.
-
|
I don't see anything wrong, you are not using latest, nor stable $ docker images --digests |grep ib-gateway
ghcr.io/gnzsnz/ib-gateway latest sha256:29ace0bde0857018ca5c7971256ce9c6a3d4622a3059f80fbac0676ed02021d8 8ae0e053c99f 9 days ago 774MB
ghcr.io/gnzsnz/ib-gateway stable sha256:c2cee07f587a557dcee03dc1808993918b47d227d4e508cd38982d92a72b899c 2f193da8f82d 10 days ago 766MB
ghcr.io/gnzsnz/ib-gateway 10.28.1h sha256:cfcc9b1e6d6c7bf268d95f555f2332432bd80f330c36fa2f2214b01c51cc9874 093f47a1131c 4 weeks ago 777MBbut that should not be an issue, unless you are using something really old. I would suggest to try with your paper account, as the issue seems to be related with MFA. Using paper will rule that out. regarding VNC any client will do. if you have a VNC client in your browser it will work(ie safari) having a FULL log file might help as well, you have pasted a small portion. |
Beta Was this translation helpful? Give feedback.
-
|
I checked out from the aarch64 branch, because I test it on my Macbook pro, attached the full logs after running docker-compose up I thought the port for VNC should be 5900, right? but when I try to access 127.0.0.1:5900, didn't see any response from the browser |
Beta Was this translation helpful? Give feedback.
-
that's important information, it could have saved us all this time. that explains ALL your problems
VNC does not work on aarch, that's explained in #81 . besides that, even if it works, on aarch (at least on my mac) you can't do 127.0.0.1:5900. you need to check which IP docker is using. on this log file there is no
Next time please put all relevant information up-front. this can be considered a duplicate of #81 |
Beta Was this translation helpful? Give feedback.
that's important information, it could have saved us all this time. that explains ALL your problems
VNC does not work on aarch, that's explained in #81 . besides that, even if it works, on aarch (at least on my mac) you can't do 127.0.0.1:5900. you need to check which IP docker is using.
on this log file there is no
socatissue and no log-in issue.10.27.1cis a really old version, I would be surprised that you can still log-i…