this post was submitted on 04 Jul 2023
14 points (100.0% liked)

Fedia Discussions

2 readers
1 users here now

founded 1 year ago
MODERATORS
 

The issue with broken images seems to be getting far worse, and that is the cause of the error 500's. kbin doesn't just skip a missing image, it just dies when trying to render a page. If I don't null out the incorrect database entries often enough, darn near everything starts breaking. I have yet to figure out why this is happening. Tomorrow, my family will be back to work and I'll have some alone time and this is what I intend to track down.

Also, I upgraded to the latest development code, so there may yet be new and exciting bugs.

you are viewing a single comment's thread
view the rest of the comments
[–] Jao@lemmy.world 0 points 1 year ago (4 children)

How is kbin compared to lemmy? Are these sort of issues that you seem to be experiencing more common with kbin as a whole? Or is it something local? I was sorting by new and I saw this poat.

[–] stack@fedia.io 2 points 1 year ago* (last edited 1 year ago) (2 children)

This instance was the first deployment of Kbin outside of ernest's control. We've had issues that no other Kbin instance has had to deal with since.

~~BTW, for those wanting to join Kbin, readit.buzz is a good instance to join should kbin.social go down (it's scheduled to tomorrow) and fedia.io get overloaded.~~

Looks like readit.buzz is gone, you should go to artemis.camp or look for other instances on fedidb.org.

[–] stack@fedia.io 2 points 1 year ago* (last edited 1 year ago) (1 children)

~~forum.fail is good too, it's managed by stux@mstdn.social~~

Edit: For anyone that still sees this, forum.fail is gone. Best go to kbin.social, or fedia if you're willing to deal with the bugs.

[–] jerry@fedia.io 1 points 1 year ago

Anything by stux gonna be good

load more comments (1 replies)