Today things seemed nearly inaccessible, between those two errors.
On the other hand, Friday and over the weekend I saw some signs that Notify services had caught up a little (posts from 2/16 finally showing up else-Fedi).
Today things seemed nearly inaccessible, between those two errors.
On the other hand, Friday and over the weekend I saw some signs that Notify services had caught up a little (posts from 2/16 finally showing up else-Fedi).
The info I got back from Ruud in the ticket I submitted:
We are aware of the issues, and are currently waiting for the latest version (2026.1) of Friendica to be released as a docker image. We hope that upgrading will solve at least some issues, they have added some fixes especially for friendica.world :-) I hope they will release that in the coming days.
I hope so as well. The site is throwing nothing but errors for me today.
As a user, today has been particularly rough -- about 3/4 of the times I've tried to do something, I've gotten:
Internal Server Error Apologies but the website is unavailable at the moment.
or
503 Service Unavailable No server is available to handle this request.
or a partial load (content but styling messed up). The problem sometime clears up with just another reload of the page, sometimes it takes a while before the system will give anything different.
And, as previously, Notify services aren't notifying, so nothing is going outbound to other servers/nodes.
Notifier doesn't seem to be active today, either.
On my side, I got lengthy 503 status periods multiple times during the day, among other errors (which I should have noted). It was the least available day in the past few months, from my interactions. By and large, friendica.world had been doing quite well; even with the occasional hiccups, I'd been thinking of asking whether we could get rid of the warning banner at the top. Yesterday argues otherwise.
The Notifier service also seems to have not processed anything of mine that did manage to get posted yesterday. All still show "Notifier task is pending."
Lacking any other answer, I will have to assume the function is broken -- which is a shame in having to manually re-contact subscribers after I start things up here, but apparently that's the way it goes.
Ugh. Yes, I meant my-place.social. Sorry.
So this week things seemed to improve -- access to the system was better, and the Notifier process abruptly caught up with the one-week backlog I was seeing. Not sure what, if anything, happened (if there was an announcement about something, I missed it), but things appear at the moment much better than they were a week ago.