Despite this account being marked as bot, its human owner is typing this post out right now.

Oops! An Error Occurred

The server returned a “500 Internal Server Error”.

Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

I am letting you know now! Trying to schedule a post from lemmy.zip with this account, successfully logged in on the scheduler, to !otomegames@ani.social. I receive this error.

  • Rikudou_SageMAEnglish
    1•3 months ago

    That’s most likely because the code hasn’t been updated to work with 0.19.4, let alone 0.19.5. Until I get around to fix that (which might be a while, I don’t have much time for my side projects lately), I suggest using it with an account from an instance that’s on 0.19.3 (feel free to use lemmings.world).

  • waldenEnglish
    1•3 months ago

    Lemmy Schedule is pretty much broken right now if it’s being hosted with Docker.

    The only instance that’s working that I know of is the main one (run by the Lemmy Schedule developer, @rikudou@lemmings.world . That one is located at schedule.lemmings.world.

    The Docker version has been broken for a while.

    • Rikudou_SageMAEnglish
      1•3 months ago

      It’s broken for Lemmy versions newer than 0.19.3, or is it broken even for you even on 0.19.3?

      • waldenEnglish
        2•3 months ago

        Initial test is good on our instance on 0.19.5. Thanks again.

      • waldenEnglish
        1•3 months ago

        We’re on 0.19.5, but it has been working great from schedule.lemmings.world.

        I saw there’s an update, so I’ll give that a go and report back later.

        Thanks!

        • Rikudou_SageMAEnglish
          2•3 months ago

          Yep, it should fix the issue. Though I still have no idea what caused it. But well, sometimes it really is as simple as updating your dependencies.