this post was submitted on 30 May 2026
8 points (100.0% liked)
Lemmy Today
328 readers
1 users here now
If you experience issues or problems with this instance (lemmy.today), this is the place to discuss them. Or if you just want to ask questions about how something works. Anything related to the instance or lemmy itself.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I ended up using the external nginx for setting rules for rate limiting and such, and there I see the real ip. It's before traffic even gets to mlmym so that's good.
Also made sure to make it use the internal Lemmy url and skip a lot of the proxy stuff I was using earlier. It seems faster now.
I implemented the headers today, so version 26.2.1 should hopefully do this correctly now.
I could only really test it in my deployment, so feel free to let me know if you have any issues!
It works! I discovered way too late that lemmy was rate limiting traffic from mlmym, because it wasnt part of my nginx config. It was lemmy itself that was doing rate limiting since all requests came from the same docker ip.
But forwarding the real ip headers fixed that, so very good. Huge thanks!
Cool. :) I think that will be a very useful feature for a lot of Lemmy admins.
Will play around with it later...!