I can't access piefed on my phone anymore, just spits out a 403. Can access it here fine. Did I get caught in some blanket IP ban?

Not sure who to ask or if this was the right place to ask, forgive me if not.

edit:

I’m using my mobile web browser and getting the issue, i don't use summit. I also tried different web browsers and proxies, still 403.

I'm getting the same, but only from the app I use, which is Summit.

It's unlikely to be an IP ban. Within the piefed software, an IP ban basically coincides with a site ban. At the infrastructure level, your IP may be banned because it was doing some pretty heavy DDOS'ing and got swept up that way. Since your user isn't banned, try switching between a mobile network and a wifi connection to see if that resolves things since your IP would have changed.

Are you trying the mobile browser or one of the mobile apps? If it is the mobile browser, try clearing the site data for piefed (cookies, etc.). There have been some cases in the past where a browser's local cache is not being refreshed properly and weird stuff starts to happen, like the CSRF tokens mismatching and whatnot.

I switched between a few networks (using VPN) and consistently get the same experience - 403 on mobile, no errors in web.

Mobile browser, or one of the apps (voyager, summit, interstellar, etc.)?

Mobile browser for web, app is Summit (only 403 here)

I also can't access the site through Summit

I see, so Summit is where the 403's are coming from. I'll do some testing on my end and see if I can figure it out.

Edit: confirm that Summit is giving a 403, but other apps are still working...investigating....

Alright, I need to step away to do actual work that pays the bill at this point, but wanted to drop what I found here before doing so.

• Summit seems to be 403-ing for piefed.social. However, I was able to log in to other piefed sites (feddit.online, piefed.ca, my dev instance) with Summit, so it's probably just piefed.social I guess?
• I tried both Boost and Voyager and they were both able to log into piefed.social.
• I was able to confirm that Summit wouldn't trip any of the user-agent related filtering in the codebase (to try to keep scrapers out of certain things).

My guess at this point is that there might be something wonky going on at the infrastructure/WAF-level. If so, then this status quo is going to stick around until @rimu@piefed.social can dive into it. My sysadmin skills are not the best when it comes to this kind of thing.

I'm using my mobile web browser and getting the issue, not summit.
I also tried different web browsers and proxies, still 403.

Sorry about that!

It was caused by an overly strict anti-scraper configuration.

Sorry to waste your time chasing gremlins!