Do we know what could have caused this cache error?
this post was submitted on 05 Jun 2023
1 points (100.0% liked)
Beehaw Support
41 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our June 2023 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Yes; configuration settings for the web server involving improving performance. Those settings have been changed back to the previous, non-issue ones. So this should not occur at this time, or again.
Is this a mistake that's easy to do for an inexperienced instance admin or just a consequence of too much fiddling and shouldn't be an issue for other instances?
Was a result of too much fiddling. Attempting to gain even better performance from a bottleneck issue due to recent user influx. It was not an error in the Lemmy instance or Lemmy-UI but rather the web server front-end misconfiguration.
Thanks for working through these issues and improving performance of the website! Very appreciated. I've been tempted recently to create my own Lemmy instance, was this a problem with an nginx configuration option? How much does Beehaw deviate from a standard Lemmy deployment?
Feel free to answer vaguely if you don't feel comfortable with giving away the details : )
was this a problem with an nginx configuration option?
Basically, this was proxy_cache_key being configured incorrectly. If you don't use the proxy_cache you should be fine.
The only thing we changed from the norm is ulimits and some nginx settings. If we figure out what works well, we'll probably create a post about how to host lemmy. If you stick to the defaults, you'll be mostly fine if your instance isn't as big as Beehaw's.
Im also considering to setup nginx caching for lemmy.ml. Did you find a configuration which works?
Not yet. Session tracking in Lemmy is pretty hard to proxy, I'll have to dive into the code to figure out why.
Have a look at this: https://github.com/LemmyNet/lemmy-ansible/pull/75
Sending proper cache-control headers from Lemmy will require some big code changes though.