The church:
dru5k1
joined 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.
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.
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.
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.
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.
Thanks for bringing it to my attention. I’ll look into it when I get a chance.
I thought I’d seize the opportunity for a little self promotion, haha. You know what that’s a good shout. I might just do that. Thank you :)
view more: next ›
My girlfriend.