[not an issue with ibeam] Account seems to be limited after a few days of running ('Gateway session active but not authenticated')

First of all, thank you so much for this project, it’s been a great help.

I just wanted to report that my account seems to have been limited after running the container 24/7 over 4 days. (This isn’t a problem with ibeam because manually running the client has the same issue. I just wanted to put it here to warn others.)

It’s been running fine the past few days with:

2021-04-23 04:40:46,760|I| Gateway session found but not authenticated, authenticating...
2021-04-23 04:40:52,701|I| Login succeeded
2021-04-23 04:40:53,809|E| Gateway session active but not authenticated
2021-04-23 04:41:46,761|I| Gateway running and authenticated
2021-04-23 04:42:46,777|I| Gateway running and authenticated
2021-04-23 04:43:46,766|I| Gateway running and authenticated
2021-04-23 04:44:46,764|I| Gateway running and authenticated

but today it started doing

2021-04-25 18:16:55,886|E| Gateway session active but not authenticated
2021-04-25 18:17:46,775|I| Gateway session found but not authenticated, authenticating...
2021-04-25 18:17:53,064|I| Login succeeded
2021-04-25 18:17:54,168|E| Gateway session active but not authenticated
2021-04-25 18:18:46,784|I| Gateway session found but not authenticated, authenticating...
2021-04-25 18:18:53,107|I| Login succeeded
2021-04-25 18:18:54,212|E| Gateway session active but not authenticated
2021-04-25 18:19:46,765|I| Gateway session found but not authenticated, authenticating...
2021-04-25 18:19:52,941|I| Login succeeded
2021-04-25 18:19:54,047|E| Gateway session active but not authenticated
2021-04-25 18:20:46,804|I| Gateway session found but not authenticated, authenticating...
2021-04-25 18:20:53,058|I| Login succeeded

I started the portal manually on my computer to check what was going on. Login through the web page still works, I still get “Client login succeeds”. https://localhost:5000/v1/portal/sso/validate and https://localhost:5000/v1/portal/tickle, https://localhost:5000/v1/portal/portfolio/accounts still return 200. However, ticker shows “authenticated: false”. https://localhost:5000/v1/portal/iserver/marketdata/history and https://localhost:5000/v1/portal/iserver/accounts gives

401
{"error":"not authenticated","statusCode":401}

[Voyz]

@andrey-ned We don’t know how official it is, but it is almost certainly a problem with Gateway and IBKR servers.

[gmara13]

Been having these active but unauthenticated error cycles pretty frequently. latest one was lasting for the the past 10 hours. i switch proxy as below:

1. Please open conf.yaml under the root folder.
2. Change the proxyRemoteHost to “https://1.api.ibkr.com”

and it immediately worked when reloading the container…FYI