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.hjsonconfig (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.mlinto your server’s search box, and subscribe to it to connect the two instances.
1 point
2 points
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
1 point
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
