this post was submitted on 07 Jan 2026
22 points (100.0% liked)
PieFed Meta
2127 readers
43 users here now
Discuss PieFed project direction, provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics.
Wiki
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Unfortunately, I'm still getting the same error.
EDIT: Just to confirm, able to login through the web UI with the same credentials.
Damn.
I logged out of Voyager and then back in again so "it works for me". Sorry.
No problem, don't worry about it. Probably an error on my end since other people don't seem to have reported the same problem.
It's just so weird that I connect to the world instance but not the social one 😱
Sorry if this is too basic but have you deleted the cache and force-closed the app before trying again? Or even the storage, if you don't have any other accounts on it to worry about.
If you don't know what all that means, then I suggest uninstalling the app (if you don't have any other accounts on it), rebooting your phone, and then reinstalling the app to try again. It's overkill, but should offer the best chance of working unless somehow that connection is being blocked by something strange and more specific to you.
I just did, tried reinstalling the app after clearing storage and cache and rebooting (my settings 😭). Tried in the web app, in another browser. Tried with, and without a VPN. It's still a no-go ¯\_ (ツ)_/¯
I think I might just migrate to piefed.world 🤔
Have you tried a different app?
Actually just tried in Blorp, and it does work.....
I had wanted to tried earlier but for some reason blorp wasn't loading anything.
But now it does work and I can login to piefed.social on it.
Which still begs the question as to why does Voyager allow me to connect to piefed.world but not piefed.social.
Dunno :) Piefed.world is a much older version of PieFed, perhaps something changed since then. But we almost never touch the logging in code...
Just as another data point: I run 1.4.2 on my instance and can use Voyager just fine.
I will try to contact the voyager dev then, thanks for the support !
I am sorry that happened to you. Thanks for the bug report:-).
No problem, thx for trying to help :)