-
Notifications
You must be signed in to change notification settings - Fork 48
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
ConnectionError: 400 Client Error: Bad Request for url: https://trader.degiro.nl/login/secure/login #107
Comments
Seems to be caused by DEGIRO's new policy blocking the default |
Thanks, will dive into this because it suddenly started on 29 december. Although I get error 429. How and where can I apply the work around? I'm used to my own code, but adjusting the source code here is another story. |
@Chavithra Can you take a peek? |
This is my log, it gives the 429 error. However, it worked flawless until 29 december. And I added a lot of 1 second sleep moments, so that cant be the source of the problem. Often my script works for a few minutes, and then fails. If I try to restart immediately, it won't start as it stops at getting the data from the exchange. edit: i just upgraded the degiro_connector.. maybe this was all I needed to do
|
Unfortunately the issue persists. I get kicked out after a few minutes. |
I solved the 429 error (it used to be possible to login multiple times at the same time), but now I get the 401 error. Which is the same as the 400 issue, only difference seems to be the 2FA. A work around would be great, @Chavithra did you have time to see where the problem is?
|
Hello folks, I guess this was fixed in the 2.0.23 from January 12th 2023 or later version since the library is working currently. Closing this issue for now. Feel free to reopen it for further update. Thanks |
I got this message when I run the client_details_table.py and I got the {"status":1,"statusText":"error"} when I run the url: https://trader.degiro.nl/login/secure/login in the browser. It seems like that url doesn't work.
The text was updated successfully, but these errors were encountered: