I’ve been working with the two suggested LemmyNet installation methods; Docker and Ansible. Neither are too wild of a setup, but they aren’t plug and play docker-compose-like, either.

I want to run a LemmyNet on a subdomain; lemmy.domain.com, and use nginx-proxy-manager to point traffic in the right direction, but it will be on the same local IP… some port changes will need to be made.

Is anyone running their own instances? Have suggestions or tips with things that helped you lean up a lemmy.subnet?

Cheers!!

  • pAULIE42o
  • . . . . . . . . . . .
  • /s
  • Jordan Jenkins ( wizjenkins@lemmy.wizjenkins.com ) 
    1·
    3 years ago

    I host my instance exactly like this with Nginx Proxy Manager. Here’s my config:

    • Block Common Exploits and Websockets Support - on
    • Add a custom location with the following settings:
      • proxy_set_header X-Real-IP $remote_addr;
      • proxy_set_header X-Forwarded-For $remote_addr;
      • proxy_set_header X-Forwarded-Host $remote_addr;
      • real_ip_header X-Real-IP;
      • real_ip_recursive on;
    • for SSL turn on HTTP/2 Support

    I had to add the custom config so that I would get the IP address of the clients and federated servers. Otherwise I was hitting rate limits on the Lemmy server.

    • pAULIE42o ( paulie420@beehaw.org ) OP
      1·
      3 years ago

      Ahh; these settings are interesting… I turned on ‘block common exploits’, but HTTP/2 support might be smart, too… yer custom location stuff is above my head, but you’ve got me sniffing a bit now. :P