Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not sure if this isn't an issue with ibkr, can authenticate but not access account #213

Open
fortnumxy opened this issue Sep 9, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@fortnumxy
Copy link

Describe the bug
Ibeam authenticates and remains authenticated as logs below show (some fields removed)

2024-09-09 19:51:21,360|I| AUTHENTICATED Status(running=True, session=True, connected=True, authenticated=True, competing=False, collision=False, session_id='XXXXXXXX', server_name='YYYY', server_version='Build 10.30.1l, Aug 27, 2024 6:01:26 PM', expires=598993)
2024-09-09 19:51:21,360|I| Gateway running and authenticated, session id: XXXXXXXX, server name: YYYY

However when visiting https://127.0.0.1:5000/demo#/ the positions demo is displayed but it is empty, the headers are there but none of my open trades are listed. I currently have one open trade and if I run IB gateway manually in a virtual machine, then in the positions demo on that virtual machine I can see the trade.

When ibeam is connected I can retrieve market data using ibind but not access any details about my account.

Expected behavior
To see my open trade listed under the positions demo

Environment
Docker Image: voyz/ibeam@sha256:79b40a57c91a2e8ab6035d89686602fb217b47a2227e8dd999368ff7484e4f0d

Additional context
I only have a paper trading account, but my account does work when I try the standalone ib gateway in a virtual machine

@fortnumxy fortnumxy added the bug Something isn't working label Sep 9, 2024
@Voyz
Copy link
Owner

Voyz commented Sep 10, 2024

Hey @fortnumxy thanks for trying out IBeam and describing your issue in detail 👍

Where is this IBeam instance deployed? On a remote servers somewhere? Possibly the difference is due to some issues in reaching the IBKR server?

Honestly, it does sound like an issue with IBKR. IBeam doesn't do anything other than start the gateway and input the credentials.

I know from experience that IBKR sometimes has some silly issues with caching on their servers. I've seen the exact behaviour you describe - having open orders and not receiving them back - on local dev deployments too. I'd suggest you address it with their support.

@fortnumxy
Copy link
Author

Thanks for the quick response...

Both the ibeam docker instance and the virtual machine I tested the standalone IB gateway with were running on my linux desktop PC in the UK (if that makes a difference).

I'll report this to IBKR later and see if I get anywhere, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants