429 Too many requests

[atpanos]

Is it only me? After some small amount of time I get only 429 on the termincheck. Any workaround? I did not change any time parameter.

[Pfuenzle]

Nope, Me and some other people (https://github.com/TobseF/impf-bot/issues/11) also have this issue, it's probably because of the bot entering the code too fast. @prok42 had the idea to use the URL that came with the confirmation email, as this way the entry of the code can be bypassed, which will probably fix this

[atpanos]

I don't even have a confirmation code. Still trying to get one for the age of 62.

[atpanos]

I set the timer up to 300 and still the same issue...

[KingLoui1986]

I also experiance the same, I also played around with different time settings. But the webpage seems to identify my connection attempt immediatly as a bot attempt. I have no other explanation for it than that. It also recognizes my very first connection attempt as a Bot and immediatly replys with 429. Does no one else have a similar same observation? Did anyone found a solution for the problem already?

[anp369]

I also have the same problem. Reloading the page by hand and entering the code by hand fixes the problem four roughly 5-10 minutes before the 429 erros pop up again. Strangely this depends on the impfzentrum. Some in my list stop working while others continue to work for some more requests.

On May 17, 2021, 23:18, at 23:18, KingLoui1986 @.***> wrote:

I also experiance the same, I also played around with different time settings. But the webpage seems to identify my connection attempt immediatly as a bot attempt. I have no other explanation for it than that. It also recognizes my very first connection attempt as a Bot and immediatly replys with 429. Does no one else have a similar same observation? Did anyone found a solution for the problem already?

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/TobseF/impf-bot/issues/40#issuecomment-842646926

[KingLoui1986]

I think this suggestion posted by @TobseF in Issue #43 could potentially be a solution for this problem as well.

Ich weiß nicht wie es sich auf die Suche auswirkt, aber wenn bei jedem Check ein "neuer Browser" genommen werden soll, dann lässt sich dass sehr einfach nachrüsten. Vielleicht wird das Cookie mitverwendet um häufige Abfragen zu erkennen. Dann würde es helfen in der locations-Schleife den Driver neu aufzubauen:

driver.close()
driver = createDriver()

Originally posted by @TobseF in https://github.com/TobseF/impf-bot/issues/43#issuecomment-843459995

[atpanos]

i don't think it will have any affect. i just ran it on windows (gradle build, java -jar ...) and it works. only on docker on my raspberry i get only 429, even on the first call.

[Pfuenzle]

Did you try to change the useragent to a windows one?

[atpanos]

i did, but somehow it does not work, you mean through the config file, correct?

[Pfuenzle]

Yes, with the config, the server should then have no idea if the client is running in docker or on a desktop

[atpanos]

#61 there was a change required to get the change of user-agent to work. on docker in windows now it works. now i will try on raspberry pi.

EDIT: still not working on raspberry pi :(

[atpanos]

@KingLoui1986 did you try the driver close solution?

[TimApplepie]

@prok42 had the idea to use the URL that came with the confirmation email, as this way the entry of the code can be bypassed, which will probably fix this

I did exactly this in my fork. Fixed the issue for me. Feel free to use it.

[GameScripting]

@TimApplepie I tried to merge & use your changes, however I noticed that your change requires me to already have received a placement code, right?

[TimApplepie]

@TimApplepie I tried to merge & use your changes, however I noticed that your change requires me to already have received a placement code, right?

Correct

[prok42]

@TimApplepie if you have the time, a pull request to get your feature merged here would be great (maybe add a switch how Vermuttlungscodes should be used - entered "interactively" or used "directly" (the latter may save you from 429, the first is maybe more robust if URL structures should change)