Between 19:45 UTC and 19:50 UTC, there was a mistake in how information was stored temporarily (cached) on Beehaw. This mistake could have allowed some people to see and use other people’s accounts without permission.
If you were using the website during that time, please check that your account settings and email address are still correct. Also, make sure that any posts or actions you made during that time are still connected to your account.
It’s important to note that we don’t have any proof that this error was actually used by anyone to do anything bad during the short time it happened.
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 : )
Basically, this was
proxy_cache_keybeing configured incorrectly. If you don’t use theproxy_cacheyou 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.Awesome! Thanks for the response. I’d love a post sometime on hosting Lemmy. I’d find it very interesting and useful!
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.
Yes.
Deviation is pretty minimal, related to configuration and customization.