• Krik@feddit.de
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 year ago

    There’s a server error (likely a HTTP 500). Jerboa can’t correctly handle them.

    • qprimed@lemmy.ml
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 year ago

      this is the correct answer. usually because the server middleware is unable to complete a request due to overload or some other issue. issues like these will get better over time as things are refined. just hang tight.

  • Acetamide@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    It’s an internal error that is shown to you. I’ve seen this before when you leave some text in the reply text box and then press back.

    I need to check whether this has been reported as an issue.

  • Zymi@dataterm.digital
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    From what I can tell this is generally a timeout error on your Lemmy instance’s part.

    Essentially the error is saying that instead of the expected JSON of posts or comments, it got a string (typically an error code)

  • its_me_gb@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    There is a high chance that the server is returning a 500 error which means the server application has failed to handle your request. Most likely your instance is overloaded.

    Unfortunately the Jerboa code doesn’t currently handle different login errors very well.