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
  • ℛ𝒶𝓋ℯ𝓃
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 months ago

    I’m also experiencing this, Cloudflare issues are periodically preventing access and Voyager for Lemmy is unable to load any content signed in through pawb periodically. This has occurred 4 times in the past 2 days, haven’t been checking much beyond that but it periodically begins working again.

      • Kovukono
        link
        fedilink
        English
        arrow-up
        3
        ·
        9 months ago

        I haven’t been hitting Lemmy that much, but it hasn’t happened since I posted.

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

        Seems to be fine-ish now. Now I’m just getting Thunder specific bugs 🥴

        Edit:maybe not. 502 error yet submits bug still here. I dunno

        • Crashdoom (he/him)OPMA
          link
          fedilink
          English
          arrow-up
          2
          ·
          9 months ago

          When it next occurs, could you email network@pawb.social and attach a screenshot of the error page? If it happens in an app, could you let me know what action you’re trying to do and I’ll see if I can pin it down in the logs! :3