Is there an issue with Voyager app recently? Today I deceided to check Lemmy and found out that nothing loads on the app, so I thought that maybe it's an issue with the app and not this instance.
So I decide to clear my app data and try to log in again, but the app showed an error about being unable to connect with pawb.social and I also couldn't access pawb.social from both the webapp and the iOS app.
Weirdly enough, I can still access other instances from Voyager as a guest.
7 Comments
crashdoom@pawb.social MOD · 6 pts · 1y
Hey! I apologize for the inconvenience. We've adjusted some of the rules after it appears they're impacting a lot more users and were overly aggressive, I'm hoping this resolves the issue and I'm really sorry for the trouble this caused.
marcuslee@pawb.social · 2 pts · 1y
It's alright, I was just a bit confused lol. I wonder if there's a way to identify Lemmy clients to be able to at least whitelist normal users, to prevent false positives
crashdoom@pawb.social · 4 pts · 1y
Paradoxically, Voyager is what I use myself, so it was allowlisted! There were a ton of rules added during the DDoS, so I’ve trimmed it down a bit 😅
marcuslee@pawb.social · 1 pts · 1y
Ah, I see
frosty@pawb.social · 2 pts · 1y
Accessing pawb.social with Voyager 2.34.0 rn.
I saw mention in Telegram announcements the other day that Crashdoom was doing his best to deflect a DDoS attack on the instance. Maybe it's related, but I'm not having any issues at the moment.
marcuslee@pawb.social · 1 pts · 1y
Hmm, I did notice that I'm getting a cloudflare message when accessing this instance from a browser. So that could be related.
frosty@pawb.social · 1 pts · 1y
Yes, the instances are protected by Cloudflare.