On Feb 14th we migrated Lemmy from its standalone Docker setup to the same Kubernetes cluster operating furry.engineer and pawb.fun, discussed in https://pawb.social/post/6591445.

As of 5:09 PM MT on Feb 14th, we are still transferring the media to the new storage, which may result in broken images. Please do still reply to this thread if your issue is media related, but please check again after a few hours and edit your comment to say “resolved” if it’s rectified by the transfer.

As of 11:02 AM MT on Feb 15th, we have migrated all media and are awaiting the media service coming back online and performing a hash check of all files. Once this is completed, uploads should work per normal.


To make it easier for us to go through your issues, please include the following information:

  • Time / Date Occurred
  • Page URL where you encountered the issue
  • What you were trying to do at the time you encountered the issue
  • Any other info you think might be important / relevant
  • Wahots
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I dunno if this is related, but I don’t think we can post to any other servers right now. Tried on beehaw and lemmy.world and got the same “cannot load post” error.

    • CrashdoomOPMA
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      9 months ago

      Is this working again? We were experiencing some networking issues, but they appear to be resolved (https://phiresky.github.io/lemmy-federation-state/site?domain=pawb.social).

      Edit: Does appear that we’re lagging a little on out-going federation activities due to the volume of incoming requests. I’ll look into setting up horizontal scaling for Lemmy in the coming days once we’ve finished setting up the final node in the Kubernetes cluster! We’re currently hamstrung for resources on the two servers we have.

      • Wahots
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 months ago

        Still getting some weirdness but I assume it will be fixed in the coming days, thanks Crashdoom :)