Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

110

Since yesterday evening, Poal.co was inaccessible until around one hour ago.

Today morning, I have noticed that the site is still accessible through free web proxies and archives, and the stream of new posts has not been interrupted.

After this, I am worried about the stability of this site. I hope this error will not occur again.

Was it a simple ? And who else was affected?

Since yesterday evening, Poal.co was inaccessible until around one hour ago. Today morning, I have noticed that the site is still accessible through free web proxies and archives, and the stream of new posts has not been interrupted. After this, I am worried about the stability of this site. I hope this error will not occur again. Was it a simple [server overload](https://www.youtube.com/watch?v=UnTyoal8R1Q&t=13m17s)? And who else was affected?

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (9).
[–] [Sticky] • 3 pts (edited )

It's not a server overload.

We've set a rate limit to prevent flood of requests from the same IP.

Those who get it have too many tabs opened on poal.

The limitation goes away after a few minutes.

Edit: https://www.nginx.com/blog/rate-limiting-nginx/

[–] • 1 pt (edited )

Could it be caused by the notification system's automatic refreshing of the number of unread ones?

[–] • 2 pts

Nope. I checked the logs and most a the rate limitations are triggered by flood of POST requests (when users submit comments).

Less than a dozen users have been rate-limited today. That's very low compared to poal's daily traffic.

I'll fine tune the configuration to reduce that again.

[–] • 1 pt

shouldn't it return a 429

[–] • 2 pts

I didn't write that error page yet.

[–] • 0 pt

Good to know, when I would change Tor circuits it would clear up which was worrying.