502 Bad Gateway when trying to access the instance through a VPN?
502 Bad Gateway when trying to access the instance through a VPN?
I use Mullvad, and yesterday I started getting a 502 Bad Gateway error whenever I tried to visit the site when connected using Wireguard. Oddly enough, OpenVPN works fine. Are the admins intentionally trying to block VPN access, or did Mullvad's Wireguard servers get caught up in some sort of filter?
3 comments
I got something similar, as I use ProtonVPN. I had repeated 502 errors.
I've had some 502 Bad Gateway in the past 24 hours and I'm not on a VPN. Ctrl+Shift+R seemed to get around it but it would happen again later.
I'm on Tor. I think it's just periodic downtime and not VPN related. Especially because 502 is an internal error.