Meta (lemm.ee)

3473 readers

13 users here now

lemm.ee Meta

This is a community for discussion about this particular Lemmy instance.

News and updates about lemm.ee will be posted here, so if that's something that interests you, make sure to subscribe!

Rules:

Support requests belong in !support
Only posts about topics directly related to lemm.ee are allowed
If you don't have anything constructive to add, then do not post/comment here. Low effort memes, trolling, etc is not allowed.
If you are from another instance, you may participate in discussions, but remain respectful. Realize that your comments will inevitably be associated with your instance by many lemm.ee users.

If you're a Discord user, you can also join our Discord server: https://discord.gg/XM9nZwUn9K

Discord is only a back-up channel, [email protected] will always be the main place for lemm.ee communications.

If you need help with anything, please post in !support instead.

founded 2 years ago

MODERATORS

[email protected]

Getting a lot of 502 nginx errors today (lemm.ee)

submitted 2 years ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Lemm.ee is a bit unstable for me today. Lemmy.world had the same issues but managed to fix it a day or two ago by changing some configurations that Ruud explained in one of his posts. Maybe Lemm.ee can try the same thing?

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 13 points 2 years ago* (last edited 2 years ago) (1 children)

Relevant section you mentioned (https://lemm.ee/post/691830):

We found that the many 502-errors were caused by an issue in Lemmy/markdown-it.actix or whatever, causing nginx to temporarily mark an upstream to be dead. As a workaround we can either 1.) Only use 1 container or 2.) set ~~proxy_next_upstream timeout;~~ max_fails=5 in nginx.

Currently we're running with 1 lemmy container, so the 502-errors are completely gone so far, and because of the fixes in the Lemmy code everything seems to be running smooth. If needed we could spin up a second lemmy container using the ~~proxy_next_upstream timeout;~~ max_fails=5 workaround but for now it seems to hold with 1.

Edit So as soon as the US folks wake up (hi!) we seem to need the second Lemmy container for performance. So that's now started, and I noticed the proxy_next_upstream timeout setting didn't work (or I didn't set it properly) so I used max_fails=5 for each upstream, that does actually work.

[–] simple 3 points 2 years ago* (last edited 2 years ago)

Thanks for quoting it!

[–] [email protected] 6 points 2 years ago

Hey! Sorry about that, there was a 2-hour period yesterday when we were experiencing some technical problems. Should be better now!

By the way, lemmy.world and lemm.ee have very different setups - lemm.ee is not using docker at all, neither are we using nginx as a load balancer. But I appreciate the tip regardless!

load more comments