I’ve been having the same issue on feddit.online (I’m the owner), where I can log in from the UI, curl, and Postman but get 400 errors from login attempts using any phone app and even Photon and Blorp on the desktop. The devs couldn’t help.

However, after waiting 24 hours or so, I was able to suddenly log in.

piefed.zip appears to be, like feddit.online, behind Cloudflare. It would be interesting to see if you can log in after they have Cloudflare entirely clear the cache. There is a potential that Cloudflare is caching a return status. I don’t know if PieFed has temporary blocks.

I had a scroll through the recent exceptions thrown by piefed.social and I might have a guess as to what is happening, but I can’t really prove it, and it is rare. I just pushed a fix and backported it to the 1.6.x branch. If @demigodrick@piefed.zip updates and this is still happening, then it is some other issue (a stack trace would be helpuful if you are able to grab one). This issue would be separate from the auth issues described by @jerry@feddit.online. More technical details below.

From my sleuthing, there are certain posts that, if they are present in the returned list of posts, will cause the API to throw an exception. This is due to the python library we use to validate our API schema (marshmallow), having too strict of a set of requirements on how urls should be formatted in Url fields of the returned json. I have changed the API schema to just be a string instead so that it isn’t validating against its url requirements.

Can confirm that I can’t open piefed.zip from Voyager now. Lemmy.zip works fine.

Maybe @Demigodrick@piefed.zip can shed some light on what is happening.

There is also a similar thread in !home@piefed.zip

https://piefed.zip/c/home/p/1062268/blorp-not-fully-loading-in-piefed-zip