sh.itjust.works Main Community

102 readers

1 users here now

Home of the sh.itjust.works instance.

Join us on Matrix Chat

founded 1 year ago

MODERATORS

TheDude@sh.itjust.works

manifex@sh.itjust.works

184

June 12 - Server Capacity Update (sh.itjust.works)

submitted 1 year ago* (last edited 1 year ago) by TheDude@sh.itjust.works to c/main@sh.itjust.works

85 comments fedilink hide all child comments

I'm aware that some of you have been getting some errors loading this instance. This was a configuration that I needed to be adjusted which has since been.

Do be patient if we run into other issues, I'll be continuously working in the back-end with others to better your overall experience.

Still a lot of capacity available!

edit: For those that are interested in the configuring changes. I was using the default lemmy configuration for the nginx worker_connections value. This value needed to be raised. Shout out to @ruud@lemmy.world over at lemmy.world for helping me out.

you are viewing a single comment's thread
view the rest of the comments

[–] Echolot@sh.itjust.works 9 points 1 year ago (1 children)

Would love to hear some more details on the misconfiguration if you want to share @TheDude@sh.itjust.works

[–] TheDude@sh.itjust.works 9 points 1 year ago (1 children)

just updated the thread post to include more information for your curious beautiful mind

[–] taladar@sh.itjust.works 8 points 1 year ago

Not sure if you already did or the default config does it but if you only have one backend in an nginx reverse proxy it might also make sense to configure the max_fails and possibly the fail_timeout options so nginx won't consider your backend down for a few seconds every time it receives a TCP error connecting to that (single) backend. max_fails=0 in the named upstream section (see http://nginx.org/en/docs/http/ngx_http_upstream_module.html#upstream ) is what you want here.