Looks like it works.
Edit still see some performance issues. Needs more troubleshooting
Update: Registrations re-opened We encountered a bug where people could not log in, see https://github.com/LemmyNet/lemmy/issues/3422#issuecomment-1616112264 . As a workaround we opened registrations.
Thanks
First of all, I would like to thank the Lemmy.world team and the 2 admins of other servers @stanford@discuss.as200950.com and @sunaurus@lemm.ee for their help! We did some thorough troubleshooting to get this working!
The upgrade
The upgrade itself isn’t too hard. Create a backup, and then change the image names in the docker-compose.yml and restart.
But, like the first 2 tries, after a few minutes the site started getting slow until it stopped responding. Then the troubleshooting started.
The solutions
What I had noticed previously, is that the lemmy container could reach around 1500% CPU usage, above that the site got slow. Which is weird, because the server has 64 threads, so 6400% should be the max. So we tried what @sunaurus@lemm.ee had suggested before: we created extra lemmy containers to spread the load. (And extra lemmy-ui containers). And used nginx to load balance between them.
Et voilà. That seems to work.
Also, as suggested by him, we start the lemmy containers with the scheduler disabled, and have 1 extra lemmy running with the scheduler enabled, unused for other stuff.
There will be room for improvement, and probably new bugs, but we’re very happy lemmy.world is now at 0.18.1-rc. This fixes a lot of bugs.
Well, I hope I’m not the only one but I cannot log in. It’s been 4 hours already. Something went wrong. I’m on Firefox mobile.
–> few hours later everything is back to normal
I am having the same issue. I’m in with Mlem, but I can not log in on the site. I even tried it with content blockers off in case there was a captcha or something being blocked.
(Safari on iOS)
Should work now
yes, it does, thanks!
You can send a reset password, and the link to reset the password will log you in as your password is updated.
However, the login button remains broken, even after password reset. Still, this provides us a 2nd way in if your browser cache gets cleared.
The XHR for the button reports back a 404 error, suggesting that login page just stopped existing after the update. I’m assuming that it will be an easy hotfix, just gotta fix the link to the POST form to point at wherever the login page went.
I’m having the same issue too, including after clearing cache and trying incognito etc.
This needs to be higher. It happens on all browsers and on jebora as far as I can tell.
Get the same but also in addition it happens in Liftoff.
It drove me nuts too and I hope admins remove the “clear your browser cache” advice from the homepage, because that will simply lock you out of your account if the login form is broken.
Right now the login form seems to work again though? Can you try again?
yes, it’s working again, at least for me
It’s weird that people seem to be having very different experiences with this. Liftoff says it’s logged in for me on my ‘world’ account, but posting/checking account details doesn’t work - Jerboa won’t login, resetting the password works once on the web, but subsequent logins don’t work.
Clearing the browser cache should fix the issue :)
Didn’t work for me on Jerboa. I cleared the app data, but I’m I still not able to login.
Edit: I’ve tried again just now and I could login on Jerboa.
I have this issue on my own instance. Neither Jerboa or Liftoff can log in to my main account (no errors or anything), but for some reason my admin account (one that pretty much sees no activity) works just fine. Thunder seems to be the only app aside of the web ui that works. Maybe an 0.18 issue?
I can’t get into my sh.it acct on Jerboa either.
Mh… some people said they tried a password reset
But I can’t confirm if this is working
I’ve tried multiple times. It doesn’t.
Unfortunately it does not, everyone having the same issue try to create account on different instance and comment on this bug in here.
it has nothing to do with cookies (and my advice is to NOT clear your cookies if you have a working session), the login form is (was?) broken, the API endpoint for the login kept returning a 404 status code
Mh… the login endpoint seems to work
Could you please share some more information?
Yes, only now, shortly before I typed that comment the endpoint always returned a 404 error.
It was a server-side error, many users in the comments confirmed it multiple times and it was a bit surprising that none were acknowledged: it had nothing to do with browser cache or cookies, the login was broken. Ruud finally acknowledged that it’s a bug related to closing registrations. Apparently closing them prevents user login.
I’m sorry, you are absolutely right!
He was working on a different issue, but I honestly didn’t give them much attention because I was investigating the cookie issue.
The issue regarding the API endpoint could be “fixed” by reenabling the registration.
The still-existing cookie issue is reported (https://github.com/LemmyNet/lemmy-ui/issues/1740) and @sunaurus@lemm.ee even fixed it already (https://github.com/LemmyNet/lemmy-ui/pull/1741)
We’re now just waiting for it to get merged
But the cookies are set just for the path