Updating to 0.18.0-rc.6
Updating to 0.18.0-rc.6
If it's good enough for lemmy.ml - it's good enough for me. Also am a bit worried about the security fixes, so not waiting for "stable".
You're viewing a single thread.
Sorry about the outage, something in rc release is very sad.
Does that mean the update is/did not complete yet?
Reason I ask is Jerboa got updated to 0.0.35 on my phone sometime mid-day today, and, when I launched it, was presented with the warning:
Server version (0.17.4) is under the minimum supported version (0.18).
Please inform your administrator and login to another instance, or sign out and use the default instance.I logged out of my Jerboa profile on lemmy.cafe, which (unbeknownst to me) deleted the profile outright, which I presume & hope is a Jerboa bug.
I can re-add the profile again, no big deal, but it can't login to lemmy.cafe, for the same server version incompatibility error:
Server version (0.17.4) too low.
It did not complete yesterday as there was a database connection problem. The syntax for the docker config keeps changing :/
Anyway, I have now updated to 0.18.0 proper, for the same reasons as well - Jerboa needed it :)
Let me know if you run into any weirdness, maybe I'll be able to figure something out.
Thank you for confirming. Just before seeing your reply Notification I saw the "BE: 0.18.0" at the bottom of the webpage, and took that as a sign that you must've resolved whatever issues you'd had.
Jerboa is now accepting my login attempts, inasmuch as it isn't giving me the server incompatibility message anymore.Thumbs-up, there. :)
Now Jerboa just thinks my username/email and password are invalid for lemmy.cafe login.
I'm just going to let the dust settle for a bit, keep trying in a few hours or tomorrow.Thank you, again!
I've tried logging in using Jerboa and it let me in. Strange thing. I assume you can log in just fine on the browser. You could try resetting your password, I used to have issues with some special characters and having >60 of them.
I've just seen reports that others are also having the same issue with Jerboa. The only other thing I can suggest at the moment is clearing Jerboa's cache and data