this post was submitted on 23 Jun 2023
6 points (100.0% liked)

Lemmy Support

4919 readers
6 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 6 years ago
MODERATORS
dessalines@lemmy.ml
6
Can't enable federation and 'private instance' at the same time on 0.18.0 (nc.gnzl.cl)
submitted 2 years ago by gnzl@nc.gnzl.cl to c/lemmy_support@lemmy.ml
6 comments fedilink hide all child comments
 

I just upgraded my instance to 0.18.0 using Ansible and I had to disable the option 'Private instance' directly on the database to get the lemmy docker up and running. I assume this is an intentional change, but should it really stop Lemmy from even running?

you are viewing a single comment's thread
view the rest of the comments
[–] Cougar@lemmy.ml 2 points 2 years ago (2 children)

I'm not sure those two settings should be compatible? If it's a private instance then it means it should not federate.

I guess it was an oversight regarding breaking changes. What error did you get? It might help some people who're experience similar problems.

[–] gnzl@nc.gnzl.cl 1 points 2 years ago

Thankfully the error was very explicit:

lemmy_1 | Error: LemmyError { message: Some("Cannot have both private instance and federation enabled."), inner: Cannot have both private instance and federation enabled., context: SpanTrace [] }

ncgnzlcl_lemmy_1 exited with code 1

With both options enabled, my instance operated as expected on 0.17.4: there was no anonymous access to anything, but once logged in you could subscribe to communities from any public instances. They don't seem incompatible at all, and my posts and comments were federated correctly outside of my instance.

[–] frozen@lemmy.frozeninferno.xyz 1 points 2 years ago (1 children)

Prior to v18, a private instance that federates could see other instances' content, but its own content would not federate. Not sure if they changed it on purpose.

[–] gnzl@nc.gnzl.cl 1 points 2 years ago

At least on 0.17.4, with Private Instance and Federation enabled, the comments and posts I made to remote communities were federated correctly to other instances. The change seems very intentional, as shown by the error message I got after I upgraded:

lemmy_1 | Error: LemmyError { message: Some("Cannot have both private instance and federation enabled."), inner: Cannot have both private instance and federation enabled., context: SpanTrace [] }

ncgnzlcl_lemmy_1 exited with code 1