Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our June 2023 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
Thanks for bringing this to our attention. Yes, Crowdsec is a protection mechanism in place to try and stop bad actors/bruteforce attacks.
I just cleared everyone on this certain blocklist, which means you should be good for now, again.
Sorry this was happening to you and other users.
Awesome, I appreciate it! Going forward, is there anything I should do to make the chances of that happening less likely?
No, this isn't your or any other users fault. It's due to the way Lemmy interacts with the backend, and was hitting some rate limit issues which made it look like an 'attack'. From a LOT of different users. Also known as a distributed denial of service attack. Not your fault!
Thanks again for bringing to our attention, I'll keep an eye on this one.
makes sense. Thanks!
Much appreciated - this allowed me back in as well, thank you for the quick resolution!
I just got this same thing twice now whenever I try to view a post outside my instance (which is problematic since federation is not working well right now). "CrowdSec Access Forbidden"
Same here. I’m a brand new user as of today and the ban suddenly happened a few minutes after first login on my home network, as I was subscribing to communities that seemed interesting to follow. After having clicked subscribe on like 5-10 communities the clicks on the subscribe link just started timing out, and then I got the crowdsec ban page when I tried to reload the page.
Odd. Are you running any js blockers like uMatrix or anything? That's the only thing I can think of on my end that tends to cause problems with this sort of thing