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?
CrowdSec is likely blocking the IP or IP range of the VPN due to high amounts of traffic or malicious activity (or because it blocks certain VPNs in general, not sure). Try a different Surfshark server/location or a different VPN provider altogether (or you can obviously connect to beehaw.org with your real IP).
Yeah it’s what I’ve been doing, but I’ve grown a habit of using the vpn when connected to a public WiFi. That’s why it took me a while to realize that it was happening, I had only opened beehaw at home, where I don’t use any VPN.
And yep, it works when using other locations.