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 Theimagehttps://.... 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.
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.
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.
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.
Getting server errors?
Are you saying you’re getting server errors accessing https://1up2down.social/lemmy ?
Hmm, I guess it was sporadic errors, it’s fine now.
Thanks for bringing it to my attention. I’ll look into it when I get a chance.
It’s probably related to the redirect.
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.
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.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.
I appreciate the deep dive, these sorts of things always have my interest!
And of course, if there’s anywhere I can help I’d certainly be happy to!
Server errors for me as well.
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.
Got one just now, sorry to tell you ha ha
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.
Works better indeed!