Fabio Manganiello on Nostr: I'm giving up on self-hosting #Pixelfed. I've faced the same issue at least 10 times, ...
I'm giving up on self-hosting #Pixelfed.
I've faced the same issue at least 10 times, with different domains, different databases, different configurations: upon server restart federation breaks.
No new messages are received, following requests are broken, external profiles are empty.
I've thought for a bit that it was an issue related to my instance keys, but it persists even if the keys remain the same.
And, tbh, I can no longer afford to "burn" domain names (if I reuse the same domain for a new instance, even if the db is completely empty, the issue persists).
I've been self-hosting federated software for years (Mastodon, Pleroma, Akkoma, Lemmy etc.), and I've never, ever faced such problems.
I stated a while ago that Pixelfed wasn't mature enough for self-hosting. I was convinced by other admins to give it another try. And the issue is still there. I must sadly admit that Pixelfed is still not mature enough for self-hosting.
I've faced the same issue at least 10 times, with different domains, different databases, different configurations: upon server restart federation breaks.
No new messages are received, following requests are broken, external profiles are empty.
I've thought for a bit that it was an issue related to my instance keys, but it persists even if the keys remain the same.
And, tbh, I can no longer afford to "burn" domain names (if I reuse the same domain for a new instance, even if the db is completely empty, the issue persists).
I've been self-hosting federated software for years (Mastodon, Pleroma, Akkoma, Lemmy etc.), and I've never, ever faced such problems.
I stated a while ago that Pixelfed wasn't mature enough for self-hosting. I was convinced by other admins to give it another try. And the issue is still there. I must sadly admit that Pixelfed is still not mature enough for self-hosting.