Login isses due to Degiro's bot detection
See original GitHub issueI have started experiencing a “Could not login” error, with the response from the server reading:
<h2>Reference: CENSORED</h2>
<h2>Remote IP: CENSORED</h2>
<h2>Identifier: CENSORED=python_bot</h2>
<h2>Date: 07/Dec/2022:11:42:43 +0100</h2>
Issue Analytics
- State:
- Created 9 months ago
- Comments:6
Top Results From Across the Web
Bot detection prevents login in some cases · Issue #604 - GitHub
After enabling bot detection in dev and testing the behavior, I am able to get into a scenario where I continually receive this...
Read more >Getting "Error getting the bot detection challenge" when ...
We've implemented a custom html login view. Everything works fine, except that when the user logs in correctly and navigates back, ...
Read more >How to detect & capture login bots
Detect attempted logins with usernames that don't exist Identify a Bot when it tries to login with a non-existent username or an empty...
Read more >github trading platform
Insight and information about trading platforms and APIs Cryptocurrency trading bot in javascript for Bitmex, Binance,. Microsoft acquired GitHub in 2018 ...
Read more >Untitled
Xoom paypal login, Positive feedbacks for teachers, Delphi center of quincy, ... Browser detection javascript css, Marten cornelissen violin maker, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I plan to maintain my fork for the foreseeable future. But if Degiro change their API so much that it’d take too much effort to adapt to the change, I’ll probably switch to another alternative at that point.
@Jakub-CZ I managed to work around the issue by setting user-agent headers:
This is my complete __request method hotfix: