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?

  • frozenA
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    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.clOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year 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