this post was submitted on 24 Nov 2020
6 points (100.0% liked)

Announcements

23285 readers
1 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
[email protected]
[email protected]
6
Federation is now enabled for https://lemmy.ml ! (lemmy.ml)
submitted 4 years ago by [email protected] to c/[email protected]
12 comments fedilink hide all child comments
 

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
}
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

It looks like you already have federation enabled, but if you're having troubles you're probably best off going to [the support community for assistance at [email protected]

[–] [email protected] 1 points 1 year ago (1 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago (1 children)

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?

[–] [email protected] 0 points 1 year ago (1 children)

I havn't looked into it yet, just using plain lemmy-ui for now, but it does look pretty nice

[–] [email protected] 1 points 1 year ago

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