Login has been disabled.
I have watchtower upgrading immich every morning and at some point it looks like login was disabled somehow? How do I undo that since I can't login?
Thank you!
13 Replies
Server Commands | Immich
The immich-server docker image comes preinstalled with an administrative CLI (immich) that supports the following commands:
I think you're the second person to say it got disabled on upgrade, which is pretty strange. Not sure why/how that happened.
thank you @jrasm91
just stop the stack and restart it.
FYI @specto since immich is under heavy development you'll sometimes need to manually do something before upgrading, so I recommend against using watchtower
Sure, I don't mind if it breaks, since it's under so much development I don't trust it for my photos yet
fwiw I don't think login was actually disabled, but this could happen in the situation the server is offline, which might have been the case for you. I'm not sure if watch tower restarts the stack in the correct order when it updates the containers.
Is that intentional behaviour?
I didn't build it like that no, but the login page asks for auth config which includes information about if password is disabled or if oauth is disabled. If that request errors out password login never gets "enabled".
I think I had it default to "disabled" so it wouldn't flash the login form in the case it was not enabled. I could change the code to show it when the call fails though.
Yeah adding an error message is probably a good idea to prevent confusion
I originally suppressed it since it was just oauth config that was loaded, but now it's both, so it should always be successful. I'll add a PR to show an error message.
Yeah so interestingly when I did follow the server command to allow logins, it let me in but showed the server as down
I haven't had that happen before but most likely, as you mentioned, it was done in the wrong order or something. I'd have to look at my docker compose further but don't have time atm
Yeah, not a huge deal. Like spupuz mentioned a restart would probably have fixed it as well.