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.
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.
There are multiple folks in Matrix who had issues, including myself. It only worked after using the old ansible code, but set the VERSION file to the new Lemmy version to 0.18.0. The new ansible sets up local networks in docker-compose and such that do not work and lead to Gateway Timeouts.
Is it safe to update via ansible?
Yes. We have one issue open having to do with site icons, but everything else is smooth.
Good to know. Thank you for your work!
I tried to upgrade via the instructions doing a
git pull
and then running ansible again and it totally broke my site with aserver 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.
Yeah, I’ll better wait for now.
You need to manually edit the configuration after, as it will overwrite it with default values
Same thing happened to me. Not entirely sure why yet but debugging seems to indicate something with the pictrs config
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.
There are multiple folks in Matrix who had issues, including myself. It only worked after using the old ansible code, but set the VERSION file to the new Lemmy version to 0.18.0. The new ansible sets up local networks in docker-compose and such that do not work and lead to Gateway Timeouts.