This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Connect to the IBGateway failed - aarch #112
Labels
duplicate
This issue or pull request already exists
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 |
|
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 |
|
Please provide the output of |
|
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 |
|
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. |
|
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 |
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 |
gnzsnz
changed the title
Repository owner
locked and limited conversation to collaborators
May 18, 2024
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Describe the bug
If 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
ib-gateway_1 | 2024-05-18 07:29:31:800 IBC: Getting main window
ib-gateway_1 | 2024-05-18 07:29:31:800 IBC: Creating main window future
ib-gateway_1 | 2024-05-18 07:29:32:452 IBC: detected frame entitled: IBKR Gateway; event=Opened
ib-gateway_1 | 2024-05-18 07:29:32:453 IBC: Login dialog WINDOW_OPENED: LoginState is LOGGED_OUT
ib-gateway_1 | 2024-05-18 07:29:32:453 IBC: trading mode from settings: tradingMode=live
ib-gateway_1 | 2024-05-18 07:29:32:453 IBC: Setting Trading mode = live
ib-gateway_1 | 2024-05-18 07:29:32:532 IBC: Setting user name
ib-gateway_1 | 2024-05-18 07:29:32:532 IBC: Setting password
ib-gateway_1 | 2024-05-18 07:29:32:533 IBC: Login attempt: 1
ib-gateway_1 | 2024-05-18 07:29:32:533 IBC: detected frame entitled: IBKR Gateway; event=Activated
ib-gateway_1 | 2024-05-18 07:29:32:535 IBC: detected frame entitled: IBKR Gateway; event=Focused
ib-gateway_1 | 2024-05-18 07:29:32:552 IBC: Click button: Log In
ib-gateway_1 | 2024-05-18 07:29:33:692 IBC: detected frame entitled: IBKR Gateway; event=Lost focus
ib-gateway_1 | 2024-05-18 07:29:33:693 IBC: detected frame entitled: IBKR Gateway; event=Deactivated
ib-gateway_1 | 2024-05-18 07:29:33:693 IBC: detected frame entitled: Loading...; event=Activated
ib-gateway_1 | 2024-05-18 07:29:33:698 IBC: detected frame entitled: Loading...; event=Focused
ib-gateway_1 | 2024-05-18 07:29:33:698 IBC: detected frame entitled: Loading...; event=Opened
ib-gateway_1 | 2024-05-18 07:29:33:698 IBC: Found Gateway main window
ib-gateway_1 | 2024-05-18 07:29:33:699 IBC: Got main window from future
ib-gateway_1 | 2024-05-18 07:29:33:699 IBC: Invoking config dialog menu
ib-gateway_1 | 2024/05/18 07:29:34 socat[116] E connect(5, AF=2 127.0.0.1:4001, 16): Connection refused
ib-gateway_1 | 2024-05-18 07:29:34:412 IBC: detected frame entitled: Loading...; event=Lost focus
ib-gateway_1 | 2024-05-18 07:29:34:413 IBC: detected frame entitled: Loading...; event=Deactivated
ib-gateway_1 | 2024-05-18 07:29:34:413 IBC: detected frame entitled: Connecting to server (trying for another 19 seconds)...; event=Activated
ib-gateway_1 | 2024-05-18 07:29:34:415 IBC: detected frame entitled: Connecting to server (trying for another 19 seconds)...; event=Focused
ib-gateway_1 | 2024-05-18 07:29:34:415 IBC: detected frame entitled: Connecting to server (trying for another 19 seconds)...; event=Opened
ib-gateway_1 | 2024-05-18 07:29:36:004 IBC: detected dialog entitled: Second Factor Authentication; event=Opened
ib-gateway_1 | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ib-gateway_1 | 2024-05-18 07:29:36:004 IBC: You should specify the required second factor device using the SecondFactorDevice setting in config.ini
ib-gateway_1 | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ib-gateway_1 | 2024-05-18 07:29:36:004 IBC: detected frame entitled: Authenticating...; event=Lost focus
ib-gateway_1 | 2024-05-18 07:29:36:004 IBC: detected frame entitled: Authenticating...; event=Deactivated
ib-gateway_1 | 2024-05-18 07:29:36:005 IBC: detected dialog entitled: Second Factor Authentication; event=Activated
ib-gateway_1 | 2024-05-18 07:29:36:006 IBC: detected dialog entitled: Second Factor Authentication; event=Focused
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=
TWS_PASSWORD=
ib-gateway
#TWS_SETTINGS_PATH=/home/ibgateway/Jts
tws
#TWS_SETTINGS_PATH=/config/tws_settings
TWS_SETTINGS_PATH=
TRADING_MODE=live
READ_ONLY_API=no
VNC_SERVER_PASSWORD=myVncPassword
TWOFA_TIMEOUT_ACTION=restart
BYPASS_WARNING=
AUTO_RESTART_TIME=11:59 PM
AUTO_LOGOFF_TIME=
SAVE_TWS_SETTINGS=
RELOGIN_AFTER_2FA_TIMEOUT=yes
TIME_ZONE=Europe/Zurich
CUSTOM_CONFIG=
SSH_TUNNEL=
SSH_OPTIONS=
SSH_ALIVE_INTERVAL=
SSH_ALIVE_COUNT=
SSH_PASSPHRASE=
SSH_REMOTE_PORT=
SSH_USER_TUNNEL=
SSH_RESTART=
SSH_VNC_PORT=
To Reproduce
Steps to reproduce the behavior. Please include information related to docker,
ex docker run command, .env file, docker-compose.yml.
Please provide the output of
docker compose configExpected
A clear and concise description of what you expected to happen.
Container logs
If applicable, add the container logs
docker logs <CONTAINER>ordocker-compose logsto help explain your problem.Versions
Please complete the following information:
docker image inspect ghcr.io/gnzsnz/ib-gateway:tag): [e.g.latest]
docker images --digests): [e.g.sha256:60d9d54009b1b66908bbca1ebf5b8a03a39fe0cb35c2ab4023f6e41b55d17894]
Additional context
Add 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
script, docker-compose.yml. Please don't expect upstream issues to be solved
here (ex. IB gateway, IBC, etc)
The text was updated successfully, but these errors were encountered: