While I’m skeptical there are many people still using fedia.io, I have been continue to try to fix the error 500 problems. These errors are caused by kbin thinking it stored database records with pointers to images (like the avatar image, images attached to posts and the like) but not actually finishing. So when certain records are pulled up (magazines or posts or users) where there is a missing image record, an error 500 exists. I’ve continued to find more instances of this and frankly I don’t know what is causing the problem. As a mitigation, I have been running cron jobs every 15 minutes to correct these broken links. This morning, I believe I chased down the cause of the last remaining disconnect and have that being fixed as well.

I suspect there are still other problems, like replies appearing twice. I will try to figure out what is going on with those as I can.

  • jerry@fedia.ioOPM
    3·
    1 year ago

    Thanks. Are you still seeing 500s even now? If so, can you point them out to me?

    • e569668@fedia.io
      2·
      1 year ago

      my profile, as well as hitstuns apparently - https://fedia.io/u/e569668 https://fedia.io/u/hitstun
      my microblog sub feed - https://fedia.io/sub/microblog … that doesn’t help you I guess lol, let’s see it appears to be https://fedia.io/m/[email protected]/microblog and https://fedia.io/m/FloatingIsFun/microblog for me

      Definitely can confirm posts that were 500ing for me yesterday are working now though, so thank you for taking the time to fix things up

      • all-knight-party@fedia.io
        1·
        1 year ago

        Just curious, are you still getting 500s? I left Fedia temporarily because the 500s just got unusably bad, but I’ve noticed I can view my profile and subscriptions without issues now, and the instance I moved to seems like their owner disappeared off the face of the earth, so I’m considering returning, but don’t want to run into 500s anymore.

        • e569668@fedia.io
          1·
          1 year ago

          So my profile as you can see still 500s. There’s also the duplicate thread / comments issue which persists.

          jerry just updated to latest yesterday, so fedia now has a lot of the new changes which should hopefully make it a little more stable, though there was a big effort to fix a lot of the 500s riiiiggghhhhtttt as he updated so I’m not sure if he snuck in the middle of those updates or caught them all. Some times I might get a 500 looking at my sub list, but it will fix itself later. I assume jerry is still running scripts which basically try to resolve those issues on a cron job so it might not work for a bit but then work later.

              • all-knight-party@fedia.io
                2·
                1 year ago

                That explains why it was never fixed, the admin running the server seems to have disappeared a week or two before i joined the instance and I haven’t seen hide nor hair of them, I even sent them a PM about that issue, but never heard anything back. Considering Fedia still has some issues and even testing the waters recently I’ve been logged out by the “invalid csrf token” problem, I think I’ll just try a different instance again, kbin.run is seeming all right, relatively small, but the owner has been recently active and is updating the instance, even directly posting about the avatar upload bug.

                It’s surprising, actually, just how few truly active kbin instances there are, and I love the hell out of Jerry, but I think he’s got too much on his plate to properly fix up Fedia at the moment, at least, not until kbin is less buggy and he has the time to spare from his many other projects, I hate to step away from Fedia, but since I quit reddit cold turkey and don’t use any other social media whatsoever I’m really relying on a baseline level of usability for all features.