It's better to sink in the cum than to cum in the sink @torres@lemmy.world You can talk to me in english, spanish or german
Ahh okay, it's good to know how it works. Now I can connect without problem to beehaw.org when using the same vpn location as before, so it's probably not blocked anymore.
I don't know how many IPs does Surfshark have for any given location, and if this was the IP that I was using before, but right now the same location gives me the IP address: 146.70.160.246
Unable to access Beehaw with a VPN
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?
