sdfpubnix

14 readers

1 users here now

Fans of SDF

founded 1 year ago

MODERATORS

SDF@lemmy.sdf.org

502 Bad Gateway when trying to access the instance through a VPN? (lemmy.sdf.org)

submitted 1 year ago by iusearchbtw@lemmy.sdf.org to c/sdfpubnix@lemmy.sdf.org

8 comments fedilink hide all child comments

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?

top 5 comments

sorted by: hot top controversial new old

[–] funchords@lemmy.sdf.org 5 points 1 year ago

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.

[–] CanadaPlus@lemmy.sdf.org 4 points 1 year ago

I'm on Tor. I think it's just periodic downtime and not VPN related. Especially because 502 is an internal error.

[–] fratermus@lemmy.sdf.org 3 points 1 year ago* (last edited 1 year ago)

the SDF lemmy server has been up and down the last day or two. Mostly down.

Edit: https://lemmy.sdf.org/u/SDF
Is there really no direct way to follow a user on lemmy?

[–] nsantoro73@lemmy.sdf.org 2 points 1 year ago

I got something similar, as I use ProtonVPN. I had repeated 502 errors.

[–] sixfold@lemmy.sdf.org 1 points 1 year ago* (last edited 1 year ago)

I'd also been receiving 502 when connecting without VPN, but now it seems to be up.

load more comments