So both lemmy and lotide were having big problems where they’d get totally overwhelmed, especially once I started federating with huge instances. At first I thought it was because my servers aren’t very powerful, but eventually I got the idea that maybe it’s because it can’t keep up with federation data from the big instances.

So I decided to limit the connections per IP address. Long-term testing isn’t done yet, but so far both my lemmy and lotide instances aren’t getting crushed when they’re exposed to the outside world, so I think it’s helping.

In /etc/nginx/nginx.conf, under the http section, I added the line “limit_conn_zone $binary_remote_addr zone=conn_limit_per_ip:10m;”

Then, in my sites-available folder for the services, I added “limit_conn conn_limit_per_ip 4;” or something similar. Both lemmy and lotide have different sections for ActivityPub and API, so it appears I can limit the connections just to those parts of the site.

It’s only been a few days, but whereas before both instances would die randomly pretty quickly once exposed to the outside world, now it appears that they’re both stable. Meanwhile, I’m still getting federated posts and comments.

  • pnutzh4x0r@lemmy.ndlug.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 months ago

    I think this is part of the recommended (external) nginx configuration for lemmy:

    limit_req_zone $binary_remote_addr zone={{domain}}_ratelimit:10m rate=1r/s;
    

    Which can be found here

    • sj_zero@lotide.fbxl.netOP
      link
      fedilink
      arrow-up
      2
      ·
      10 months ago

      That explains a lot. I run everything on bare metal, and I don’t think the bare metal instructions included that.