Too many requests error opening multiple browser tabs

Is it just me…

…or are other AB users seeing effects of (possibly) backend AB webserver changes?

What used to take seconds (clicking on Notifications button, and then right clicking each new “<name><followed> has published a new image” and opening each in a new browser tab) now is fraught with delays, “Too many requests” errors or the tab being blank with a new login dialog, all of which means that it now takes minutes at a time. Same thing with simply marking a notification as Read… If I go as quick as I used to be able to a few weeks ago, now I’ll get 3 or 4 or 5 marked and then I’ll see the dreaded “Too many requests” error. I know I’m quick, but, really??

Anyway since I follow a fair number of folks, my Notifications queue always has at least 50 or so items per day!

So like I said at the beginning, what took just seconds to do now takes minutes because of the excessive errors issued by the AB pages that I try and open.

Please don’t suggest that this is related to my browser - I’ve got a Group Policy configured to clear out cookies etc every time I close the browser (Brave) and it is always fully updated. The AB webpages are spawning the error messages… This just started happening within the last few weeks and I’ve made no other major system changes on my PC.

So, is anyone else seeing this behavior?

Perhaps @Salvatore Iovene could chime in…

Hi Gordon,

I have not made backend changes that would affect normal browsing behavior.

AstroBin does enforce rate limits to protect the platform from crawlers and automated traffic. These thresholds are set high enough that normal user interaction does not trigger them.

I checked your recent activity logs. There were two short bursts that resulted in 409 responses:

• One related to the API endpoint that retrieves the notification count. That endpoint is designed to be called at most every 30 seconds. It appears something caused repeated calls in a short time window.

• One related to forum tag generation during posting.

The 409 response in these cases is not a functional error. It simply indicates a request was temporarily rejected due to rate limiting. I’ve removed the visible error message for that condition (currently deploying to the server) and am tightening the client-side throttling for those endpoints so repeated calls cannot accumulate.

If you continue to see this issue, please open a support ticket and I’ll investigate further. That would not be expected behavior under normal conditions.

That should address the issue.

PS: to make the AstroBin web app is up-to-date, close all AstroBin tabs first.

Thanks for reporting and help me make AstroBin better,

Salvatore

Related discussions