• Blaze (he/him)@sopuli.xyzOP
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Seems like a nice instance, thanks for sharing! You might want to create a local community to discuss your instance management, who you are, etc.

      • Dru5k1@lemmy.1up2down.social
        link
        fedilink
        English
        arrow-up
        6
        ·
        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.

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

          Late to respond, but I was in perfectly well just now!! Great job on getting it sorted :)

              • 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
                  3
                  ·
                  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 the heads up. You’re absolutely correct. To delve a bit deeper, in case you’re curious: my oversight in not mounting the mnt directory for Pictrs results in a reset of both the database and manifest each time the system restarts or updates. As a result, even though the entry is stored within my instance’s object storage, the corresponding manifest and database entries are missing. I will indeed need to reupload them. Once again, thanks. On a related note, I have openings in n my moderation team. If you’re interested, I would genuinely welcome the opportunity to collaborate with you. Honestly, I’d welcome the chance to collaborate with all the kind-hearted individuals in this thread who took the time to test my instance. Thanks, everyone. This is what makes Lemmy special.

          • 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.