Hi all. I was recently made aware that people have been getting error 429’s and other error 500’s when visiting fedia.io. My hope/expectation is that those will no longer happen now that I’ve moved back to a bare metal install, but if you do experience that, please comment below, or if that doesn’t work, send me an emai to jerry@infosec.exchange.

Thank you!

  • bacon_saber@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Got one just now while hitting next page in my feed.

    /?p=4

    500 Internal Server Error Sorry, something went wrong on our end. If you continue to see this error, try contacting the instance owner. If this instance is not working at all, check out other Mbin instances in the meanwhile until the problem is resolved.

    • e-five@fedia.io
      link
      fedilink
      arrow-up
      0
      ·
      9 months ago

      @jerry there was a super fast follow up to 1.4.0 to fix a 500 that got introduced https://github.com/MbinOrg/mbin/releases/tag/v1.4.1 (the big warning at the top is to make sure people read the 1.4.0 upgrade docs since this release came in so quickly after it, in case they’re running <1.4.0, but you should be all set since you already upgraded)

    • jerry@fedia.ioOPM
      link
      fedilink
      arrow-up
      0
      ·
      9 months ago

      I applied a fix that (hopefully) resolves this new problem. Please let me know if you continue to see it.

  • kbal@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    In case it’s not obvious that it’s gone wrong just now, it’s started giving me 500 and 502 errors. … and now it’s stopped.

  • eruraindil@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I am seeing a 500 error when trying to login using Interstellar a new kbin/mbin app in development.

    Trying to browse fedia without logging in on the app throws a generic something went wrong error.

    They confirmed recently in their GitHub that they do support mbin and kbin.melroy.org works. login and in guest mode.

    I can throw up a screenshot as soon as I figure out how to add an image.

        • cocopoops@fedia.io
          link
          fedilink
          arrow-up
          0
          ·
          7 months ago

          just tried testing this it still seems to give a 500 error when trying to login from the app

          • eruraindil@fedia.io
            link
            fedilink
            arrow-up
            0
            ·
            7 months ago

            The app was updated last week and that seems to have fixed the issues for me at least. It’s pretty bleeding edge so makes sense that there’s some teething. I’m just happy that there’s some interest in the non Lemmy side of things over here in the threadiverse.

            Thanks Jerry for your assistance last month!

  • sudo_xe@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    Okay not an error 429 or 500 this time and just some noncommittal Error with no real message in a logged-out UI (that also returns to normal upon refresh) that I once again encountered for the first time.

    I upvoted this very post, e-five’s comment, and then your reply in rapid succession. The first and last actions went through, but there was a circle indicator beside the “More” option on e-five’s comment and the page ultimately loaded https://fedia.io/ecf/3871174?choice=1 and thus the error page. We’re both on the same instance and I shouldn’t be blocking them or running any script that should mess with upvoting btw


    After going back from the error page to submit this comment, hit submit button only to be redirected to https://fedia.io/m/fedia/t/552719/-/comment without the comment having posted. I find the page usually needs to refresh to send a message but this was the first time I ended up on a different page when trying to write something?

    • e-five@fedia.io
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      Everything about your post is slightly indicative to me of javascript failing, for some reason.

      So many actions taken, upvoting / boosting / replying, do javascript actions. However, all of these things have fallbacks in the case either: javascript hasn’t fully finished loading on the page yet or javascript requests failed.

      For instance, if javascript had failed when I clicked reply to your message, instead this page would’ve loaded for me https://fedia.io/m/fedia/t/552719/Request-for-errors-on-fedia-io/comment/3937344#add-comment but since it worked, all it did was add a text box under your reply

      As I said this is true for all other actions, so when you vote or boost there are also http GET routes that handle those requests.

      It’s hard for me to guess more than that, it could be the JS is loading a bit slow and you click before the page finishes loading, or it could be a different error like maybe the request fails. There might also be something else involved, I’d have to double check but mercure might involve itself in dynamic page updating as well… Do you happen to notice if pages are still loading when you take actions, or in fact just browse with javascript disabled? There’s also that, last I checked, all the JS files had defer on them so don’t block page loads, which is what makes this more likely to happen. Whether that’s good or not, I can’t say, it’s been like that since I first looked but might require more research to know whether it can be split between JS that should block page load and JS that can be deferred

  • sudo_xe@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Got an error 500 the other day when trying to visit /m/theonion@midwest.social, what was strange was that it was not rendered “within” the context of site UI but I was shown a totally white page bereft of any decorations except the error message on the top left (first time I ever saw this).

    Got an error 500 just now from replying to a message, it was a typical error 500 taking up the main body column on the site (appeared to be logged out and all), and then returned to normal after refreshing.