/kbin meta

12 readers

1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago

Messages / Notifications are unreadable - accessing page gives 50X error. (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

@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.

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

@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