-
Notifications
You must be signed in to change notification settings - Fork 117
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
New constant occurrence of 'Invalid username password combination' #100
Comments
Hi, I tried it two days back and it works. I did come across your issue as well but on 16th Sep. (Friday), it was working again. It could be an issue from IBKR's end. I will try again on Monday and update. |
Hey @zeeb0tt thanks for outlining your issue in detail 👍 Unfortunately, this is a problem that we're aware of and it seems to be on the side of IBKR - you can see similar problems appearing in other issues in this repository. Hence, I'd encourage you to report it to IBKR support and try to solve it with them. There hasn't been any updates to IBeam around the time you're reporting. Thanks for chipping in @stanj98 👍 |
Hi, I have the same problem. Regardless of the configuration, it shows me the same "Invalid username password combination" message. The only difference I see in my authentication is that now it asks me to confirm my login from the IBKR app with a floating notification on my mobile. When I run the gateway directly it works for me without any problem, I put in my credentials, I get the mobile notification, I approve it and I access it correctly. For this reason, I think the problem is the notification that reaches the mobile, I don't know if this is contemplated in ibeam. Greetings. |
Hey @Raulcr93 thanks for chipping in. The mobile auth and notification is also handled by IBKR not IBeam, hence once again I'd suggest addressing it with their support. Other users have also observed that things are different when the Gateway is started locally, however there hasn't been any pattern observed yet that could suggest why there is a difference. Feel free to propose a solution if you can think of something though 👍 |
Also experiencing this problemo -- has anyone resolved this by contacting IBKR? They seemed to be unhelpful, but maybe I'm not "saying the right thing" or "asking the right question?" Appreciate all the work on this, thank you! |
hey @ckcollab I'm sorry, but this has been an ongoing issue since I've started working on IBeam, and it happens with different severity for some users, while not at all for others. I'd love to help more, but IBeam only serves as a thin layer on top of the Gateway. Unless we can show that the credentials are scrambled somehow when they're input - all we do is copy paste them into two fields -, there's little we can do other than trying to address this with IBKR |
@kadnan that same username/password should work again on your IBeam instance on some other attempt. TWS is a separate trading platform altogether, so there it could work when it fails using the Gateway. Also I've been seeing the issue with the page not loading. IBeam only just loads whatever the Gateway will serve it, if there's some Javascript/HTML/rendering issues then that's again on IBKR side. I'd suggest you highlight this issue with them. I've found this loading issue appear when the connection is particularly slow. |
@Voyz it's okay! Ty for all the hard work Things are working ok now, in my case I believe I was IP banned from too many attempts at one point, changing my IP resolved the issue! |
That's very interesting @ckcollab! What makes you think so? This would be very useful for other users to know! |
When I would go to the IB docs pages they would say "Access Denied" until I turned on my VPN/changed IP :) |
@ckcollab you're right! Using a VPN does help! I changed my VPN to UK. |
Glad to help! @Voyz |
Hi, Here is the most recent logs that I got:
I also believe this is an issue with the IBKR side. But, from what I think, if there is a way to automatically restart the docker container after a pre-defined time (say after a few hours), we can bypass this issue. Or as a second suggestion, we can wait longer if we see more and more Or please let me know if there is another way to fix this. Thank you. |
Hey @Wenuka - thanks for sharing your observations 👍 Honestly though, I really couldn't comment much on this. The errors seem quite sporadic, and there's little to draw conclusions from. Now as for your points:
I honestly wish I had some other ideas on how to handle these issues, but there isn't any indication that could help us tackle it. The best thing we can do is to let IBKR know of these problems, so make sure you highlight it with their support. |
Hey guys, just wanted to share that I've noticed this error happening if the process of logging in happens too fast. I used a selenium script to auto authenticate with the Gateway (a side project, other than IBeam), and if it just fills the creds out and instantly submits, the 'Invalid username password combination' occurs. Something to think about. We already have a 5-second buffer there, but possibly there's something else we could do here: ...
user_name_el.send_keys(account)
if key is None:
password_el.send_keys(password)
else:
password_el.send_keys(Fernet(key).decrypt(password.encode('utf-8')).decode("utf-8"))
password_el.send_keys(Keys.TAB)
# small buffer to prevent race-condition on client side
time.sleep(5)
# submit the form
_LOGGER.info('Submitting the form')
submit_form_el = driver.find_element(By.CSS_SELECTOR, elements['SUBMIT_EL'])
submit_form_el.click()
... I tried seeing if it would run some request upon typing the creds, but it doesn't seem to. I wonder if it runs some JavaScript code when you do that, and maybe it doesn't finish by the time we submit. I decided to add a functionality where we'd increase that buffer timeout on subsequent occurances of this error. There's two new env vars that define the starting and maximum waiting time: |
Thanks @Voyz for your quick response and I agree. Just now I managed to add the second suggestion (waiting increase interval of 1-5-30-60min). Incase some one else is interested, all what I did was to add the following in the
This waits 15-30-60-120 minutes as for me it is okay. But you can modify it as you want. I will update you incase this solves the problem in a few weeks. |
hey @zeeb0tt @Wenuka @ckcollab and others - there is a new WIP version Run the most recent See #147 for more details and report any observations directly there. Thanks 🙏 |
I'm going to close this issue due to inactivity. Thanks for your contribution and please feel free to request a reopen if you'd like to continue the discussion 👍 |
Describe the bug
I've been using voyz/ibeam for some time now. Suddenly as of this morning, it reports an invalid username password combination. I can login to IB directly with exactly the credentials provided (copy + paste) but voyz/ibeam will say this at all times now. It had been working flawlessly every day for months.
Although I did notice when I logged in via the web UI @ IB that the URL looked a little different the first time around.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Typically the authentication is successful and 2FA is triggered.
Environment
IBeam version: 0.4.3
Docker image or standalone: docker
Python version (standalone users only):
OS: Windows 10 Home
The text was updated successfully, but these errors were encountered: