Closed bigretromike closed 7 years ago
Oh, also the BAN notification vanish after some time - which looks like the ban is no more
@hidden4003 you did great job with current ban prevention system, could you make it perfect ?:-)
HTTP ban is unavoidable I'm afraid as there is no authentication like with UDP so essentially they only are able to control by IP.
Oh so http and UDP are different. Maybe slowing down http traffic would help ?
Read this comment: https://github.com/japanesemediamanager/ShokoServer/issues/379#issuecomment-256856048 I don't think there is a solution unless anidb allows to login for http api as well.
I don't see anything that login would resolve other that they use flood defense and lowering number of packets would 'maybe' not trigger it. But you are the expert of that matter her so I leave it close as is. thanks for info
what i personally dont get on this is that there never was an http ban til these newest updates. i could run the queue for hours on hours before getting an udp ban at times. getting http banned within the half hour almost all the time tho.
so are we getting more info from anidb now because we are also using http? cause it wasnt like this before at all.
the server is practically useless for me in so many ways because of these bans.
I think your misunderstanding the issue, something changed on AniDB's side which they have not been able to pinpoint thats causing the issue.
for me its not "something" but more of flood-prevention on firewall - also if thats the case the easiest way would be "tell use the limit anidb" and we tweak our script so it wont flood that much or just randomly put values and testing it against flood. so more flood for them as more people test the script :-)
Also there been so much time that there could be a change made to our system that made it work faster/stronger, and in long run (few hours) that 1-2 query per second or minut could lead to flood detection.
While importing collection to fresh db in current master after some time I got hit by BAN. Its not instant ban as the current system does decent job in preventing it . Maybe its because of few hours of asking anidb or one more second per request... dunno . Just wanted to inform that current system is a god send compare to pre 3.7 ones but still some tweaks are needed.