User cannot log in from mobile app
Starting from 140 I believe, the only user cannot log in due to password mistmatch.
I never change my password.
I use the true admin user to reset his password, and can log in from the web.
Change his password back to his original one.
Can log in from the web.
Both times he cannot log in from iOS mobile app.
35 Replies
:wave: Hey @BitePa,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.Now I'm on 142.0. Docker Compose. Been updating from this instance all this time. It's been working fine up until 139.x.
This error does not prevent logins. Can you share your entire mobile app logs?
Got a few more.
Wait, are both the server and the iOS app up to date?
Server at 142
Can you try login via local ip?
Ah. I can log in. Weird.
No changes on the front proxy nginx.
Hmm
The not found error shows that the server is not on the latest version. Maybe caching issue? Try resetting your reverse proxy to be sure
Updated server to 142.1, and have these errors:
look like networking settings issue
you can access fine via local ip?
Right now the public endpoint is responding, although it's slow
Previously, that
<doctype html> from one of the recent screenshots most likely came from Nginx when it wasn't able to reach backend / Immich.@Alex @Sergey Katsubo it seems to work locally. I double double checked the proxy doc https://immich.app/docs/administration/reverse-proxy, and it hasn't been changed for a long time. Now user can't log in via Internet.
try restart your proxy
Already restarted numerous times.
Being able to log in from the internet using web browsers doesn't mean it works with mobile app, right?
You can enable debug logging in Immich server and see incoming requests in logs - details here https://discord.com/channels/979116623879368755/1415993129374449775/1416034573749452870
I suggest the following plan:
1. Enable debug logging.
2. Log in using web. Make note of exact timestamp when you do it. Check logs at/around this timestamp to make sure your login requests are shown there.
3. Try to log in using mobile. Make note of exact timestamp when you do it. Check logs at/around this timestamp.
Post here logs from steps 2 and 3.
Ideally - check/post Nginx logs too.
Yeah. Ok. Will do it.
Been having the troublesome CPU-hog syndrome lately. Hope to also get to the bottom of it.
Log for logging in from local web
Connecting to server in mobile app after specifying server URL, locally.
continue from above, using username and password to log in.
Local, web browser /auth/login works. I can see the login page.
From front end, I get:
192.168.1.1 - - [20/Sep/2025:09:09:29 +0800] "POST /auth/login HTTP/1.1" 404 74 "-" "Immich_iOS_1.142.1"
curl -v -XPOST https://photo....com/auth/login
ah.... it should be /api/auth/login, not /auth/login
got it. In mobile app, the server URL has to end /api... duh
can this be improved to handle /api better, without user specifically specify it?
Its not required. You probably are intercepting or breaking the .well-known endpoint with your reverse proxy
I have this:
location /.well-known/immich {
proxy_pass http://192.168.1.123:2283;
}
keepalive_timeout 70;
gzip on;
gzip_min_length 10240;
gzip_types text/plain text/css text/xml text/javascript application/x-javascript application/xml;
location / {
proxy_pass http://192.168.1.123:2283;
}
Youre missing an equal in the location to start, please check our docs
good catch @Zeus ... me bad.... missing =
following the official doc, I still can't get reverse proxy working without using /api. I ended up using it and get it over with.
In Nginx logs and Immich logs
are there requests to
/.well-known/... ?
I'm wondering if the previous (incorrect) result is cached in the app.