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 September 2024 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.
Hi, I recently encountered this issue when trying to access the instance (both in the browser and Jerboa) while using a VPN. I don't know if this is just an issue with the one I'm using (Surfshark) but I didn't have this issue before.
I imagine this security layer was implemented recently, and that's why it didn't happen before.
Is this intended, or is it just the filter wrongly taking the VPNs IP as a malicious one?
I currently don't see that on any block list used by our instance of crowdsec.
Probably why it's working now. Thanks for the explanation! Now I know why it's happening if it ever happens again