let’s see if the newly released lemmy 0.18.1 solves this problem (to the tech team: lemmy-ansible has also been updated).
a tip that I’ve heard: due to the changes in the path of some .js files, after the upgrade, those of us still using the browser (instead of apps) will need to refresh monyet.cc to get the old path out of browser cache.
keep in mind that this 0.17.4 to 0.18.1 upgrade is a major one, touching almost all lemmy components. so, backups will need to be taken, and we’ll all have to keep our fingers crossed that the upgrade completes without any complications.
here’s an issue that I think a couple of other instances have run into: https://github.com/ubergeek77/Lemmy-Easy-Deploy/issues/26 (it’s not from the lemmy-ansible repo but I think this developer tries to follow lemmy-ansible’s docker file quite closely)
from a glance it seems to involve the /etc/hosts file interacting with docker dns, causing lemmy-ui to fail when finding the site icon (so if you haven’t set that then you probably won’t encounter this issue)
see especially this comment where the lemmy easy deploy developer does not recommend running the default postfix container included in the docker file due to vps hosts blocking port 25.
so, you’ll probably have to work out another way for users to receive a password reset email (and there is some further info about using sendgrid in the issue that may help).
edit: I just realized I’ve never actually tried out the password reset function (also haven’t heard any of the other users discussing it), so if my assumption is wrong, and it is working properly for monyet.cc, then please disregard this.
let’s see if the newly released lemmy 0.18.1 solves this problem (to the tech team: lemmy-ansible has also been updated).
a tip that I’ve heard: due to the changes in the path of some
.jsfiles, after the upgrade, those of us still using the browser (instead of apps) will need to refresh monyet.cc to get the old path out of browser cache.keep in mind that this 0.17.4 to 0.18.1 upgrade is a major one, touching almost all lemmy components. so, backups will need to be taken, and we’ll all have to keep our fingers crossed that the upgrade completes without any complications.
all the best to the tech team!
Hope so, but i heard of the same problem from lemmy.world after they updated to 0.18.1, so maybe it will be fixed in stable release.
the stable release is out, at least for 0.18.1 it is, and lemmy.world has been upgraded
We’re upgrading hopefully tonight!
that’s great news :-)
here’s an issue that I think a couple of other instances have run into: https://github.com/ubergeek77/Lemmy-Easy-Deploy/issues/26 (it’s not from the lemmy-ansible repo but I think this developer tries to follow lemmy-ansible’s docker file quite closely)
from a glance it seems to involve the
/etc/hostsfile interacting with docker dns, causing lemmy-ui to fail when finding the site icon (so if you haven’t set that then you probably won’t encounter this issue)edit: okay, I think https://monyet.cc/pictrs/image/9af04c84-4810-436c-9263-b550eb2de176.png is the site icon, so you have it set
Thanks for shaking that out for us!! :)
you’re welcome.
I hope I’m not bombarding you with issues, here’s another one, but it can wait until after the upgrade: https://github.com/ubergeek77/Lemmy-Easy-Deploy/issues/38
see especially this comment where the lemmy easy deploy developer does not recommend running the default postfix container included in the docker file due to vps hosts blocking port 25.
so, you’ll probably have to work out another way for users to receive a password reset email (and there is some further info about using sendgrid in the issue that may help).
edit: I just realized I’ve never actually tried out the password reset function (also haven’t heard any of the other users discussing it), so if my assumption is wrong, and it is working properly for monyet.cc, then please disregard this.
deleted by creator
Thankfully we’ve got external email - we ran into this or a similar issue. Thanks! :)