Skip Navigation
/kbin meta @kbin.social Anomander @kbin.social

Messages / Notifications are unreadable - accessing page gives 50X error.

I have two unread messages I can't access, as going to the notifications page results in a 50x error every time.

Has anyone else encountered this, or know of a fix?


This seems related to having left a comment, that got replied to, on a post that Kbin sees as "deleted_by_author" - after deletion, no comments are visible on the Kbin post.

The original post on Lemmy appears intact, while the version on Kbin is empty. Navigating to my own comment there is a blank result, but if I navigate via the 'reply' function it's still available.

If Kbin is trying to load a reply it also believes does not exist, that may be breaking things - but it leaves my notification box permanently broken because there's no way to 'clear' that paradox post from the listing.

12
12 comments
  • Update: Ernest AnonymousLlama made a change to the error message for an upcoming release of Kbin. Error 500 messages indicate that the bug is already known about and a fix is actively being worked on. See https://codeberg.org/Kbin/kbin-core/commit/39072db72716b8996f627dd7715804064a9e781c

  • I think we need to make an issue in Codeberg for this.

  • I've been having this problem for nearly a month. I assume a fix is in the works, because this error breaks the entire software. Without notifications, how are you supposed to have discussions on kbin?

    • Yeah, I certainly hope so. Mailbox is perma-busted. I saw the notification number change when a new reply came in, but had to check for replies 'manually' in order to figure out where someone responded.

      It seems like this may be linked to getting a reply on a post that was deleted, as none of the comments in that post are accessible anymore; did you reply to something that was deleted later, around the time your mailbox broke?

      • It's possible, I can't recall. I also had to manually go through my comments to find your reply.

  • @Anomander

    I've had kbin show me a 500 once or twice, but it was because my ethernet cable had slipped the socket.

    I've gotten more complex custom errors of indeterminate type, generally when posting, but typically the error is in error, as the post completes as expected.

    • Not "500" - it's labelled as an "Error 50x" and returns the downtime page prior to the server upgrade;

      I've had kbin error while posting a few times, but that was back prior to the server upgrade when accounts were logging back out every five to fifteen minutes - this is generating the same error page as then, but is a new problem leading to it.

      • @Anomander

        This is the second error I described.

        However, I was not trying to tell you what error you experienced, only offering my experience for comparison, or to add to the list of things you're hearing about.

        Cheers and Good Luck

12 comments