Instructions for running your own lemmy instance.

For the moment, lemmy.ml is using an explicit allowlist for instances we federate with. If you currently run an instance, and would like to be added to join.lemmy.ml:

  • Let us know either on !lemmy_instances, or commenting here.
  • We’ll add you to our allowlist.
  • Add this block to your server’s lemmy.hjson config (for open federation):
federation: {
  enabled: true
  tls_enabled: true
  # allowed_instances: lemmy.ml,other_instance.tld,... uncomment this to use an allowlist
}
  • Type !announcements@lemmy.ml into your server’s search box, and subscribe to it to connect the two instances.
    • SynapticOddity
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Thanks! I’m just missing a bunch of comments (but not posts) from Lemmy.ml. I thought lemmy.ml were running on an allow list? Might be something else thought.

      • phoenix591@lemmy.phoenix591.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        they moved away from the allowlist and now only block some. federation with my own instance just worked after I got updated to 0.18.1 and adjusted my nginx config

        • SynapticOddity
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          good tip! I upgraded to 18.1 now. Hopefully fixes the missing comments.

          • phoenix591@lemmy.phoenix591.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            part of it was http signature expiration, showed up as

            WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Header is expired
              0: lemmy_server::root_span_builder::HTTP request
                        with http.method=POST http.scheme="http" http.host=mylemmyinstance.com http.target=/inbox otel.kind="server" request_id=453c8a92-7bb5-4b7e-a4ad-212e91167d4e http.status_code=400 otel.status_code="OK"
                     at src/root_span_builder.rs:16
             LemmyError { message: None, inner: Header is expired, context: "SpanTrace" }
            

            in the logs, and that was fixed

            the other part was some nginx config changes

            • SynapticOddity
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Brilliant. i think both were fixed with the ansible update. Thanks for helping out phoenix!

              Not sure if you are also knowledgeable about wefwef, I have another question: I have installed wefwef on my host. Works great! Except I can’t get watchtower to update it. I have to do a manual restart of the wefwef constrained every time. I’ve tried to increase the wait time, but no luck. Any tips?

                • SynapticOddity
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  1 year ago

                  I recommend it. It’s a great smartphone frontend. Still missing some small features, but super great usability.