• Dru5k1@lemmy.1up2down.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            That was my initial thought, but in the end it was related to pictrs. It was throwing sever errors due to not being able to find pictrs images.

            • russjr08@outpost.zeuslink.net
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 year ago

              Just as a heads up, I noticed that your user avatar doesn’t seem to be loading properly, and going to it directly gives a The image https://.... cannot be displayed because it contains errors. message, which also occurs with your instance’s site logo as well. Pictrs might still be having some issues for you, or if you made any major configuration changes you may need to re-upload those images.

      • Dru5k1@lemmy.1up2down.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Thanks for letting me know. The issue was related to the incorrect configuration of pctrs. It has now been resolved and the Server Error should have subsided.

          • Dru5k1@lemmy.1up2down.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            Typical. I forgot to restart, it should be all good now :)

            You may need to clear your cache for the new configuration to take effect, and any broken images will be fixed sequentially.

            For anyone else who experiences this Server error… In my case, I mistakenly thought pictrs ‘s docker container was fully stateless, when configured with object storage. Long story short, it isn’t. You should still mount the mnt directory as it contains db and metadata files.