• Dessalines@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      Yes. We have one issue open having to do with site icons, but everything else is smooth.

    • binwiederhier@discuss.ntfy.sh
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      There are multiple folks in Matrix who had issues, including myself. It only worked after using the only ansible to VERSION=0.18.0. The new ansible sets up local networks in docker-compose and such that do not work and lead to Gateway Timeouts.

    • Tugg@lemmyverse.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I tried to upgrade via the instructions doing a git pull and then running ansible again and it totally broke my site with a server error message. I ended up reverting back to 0.17.4.

      EDIT: It looks like they added some extra NGINX proxy stuff in there. All that broke my instance and I had previously just deployed via ansible following the instructions on their page. I would stay away for now.

      • bagog@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Same thing happened to me. Not entirely sure why yet but debugging seems to indicate something with the pictrs config

    • gnzl@nc.gnzl.cl
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I just upgraded via Ansible and the only issue I ran into is that on 0.18.0 you can’t enable Federation and Private Instance at the same time. I had both enabled on 0.17.4 and when I upgraded, the Lemmy docker wouldn’t start because both options can’t be enabled together anymore. I had to disable Private Instance directly on the database to get my instance up and running again.