Unable to access through web interface
Fairly recent install of Immich on WSL using docker compose. Working fine for a week and then I get this on the web interface:
Error: 500 ()
Stacktrace
Error: Error: 500
at Object.st [as ok] (https://immich.xxx.net/_app/immutable/chunks/I4ASpmdk.js:1:5945)
at async Promise.all (index 1)
at async c (https://immich.xxx.net/_app/immutable/chunks/cib8wyio.js:1:524)
at async o (https://immich.xxx.net/_app/immutable/chunks/Bri_YyT6.js:1:177)
at async it (https://immich.xxx.net/_app/immutable/nodes/0.Dlm4x30H.js:1:1999)
at async $e (https://immich.xxx.net/_app/immutable/chunks/D1UzYfOZ.js:1:15856)
Check all logs (as far as I know, am a newbie to docker and Immich). I can see not obvious error message. Web searches does not reveal much, other than maybe postgres related (?). Any advice where I would look?
26 Replies
:wave: Hey @Oneklema,
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.Does connecting via local ip work?
What url are using for local access? Any browser console logs?
Nothing sticks out in the logs, so maybe
Also I have no idea if localhost works for accessing services in the wsl context from the windows host
It can, but Windows firewall is known to stop it
here is the console log.
Same thing. Are there anymore logs? When attemtping? Also can you try accessing using ip instead of localhost just to rule out
Also is the DB on an ntfs file system?
Using IP is the same result. No more log entries in the console. I have looked and sent all of the logs I am aware of. Not sure where else to look.
I have a nextcloud AIO on the same server and it is working properly.
file system for data is exFAT. postgres DB is on NTFS SSD. Could that be a problem?
Yes.
Postgres cannot be an ntfs file system. It can lead to very unexpected behavior. See install note here: https://immich.app/docs/install/requirements/#special-requirements-for-windows-users
I'm surprised it even runs at all
Why didn't think to ask because was working prior
yes, it worked fine for about for a week with about 500G of data. Also, the link you sent does mention using it with WSL 2.0 (which is what I am using). I am frankly not sure what type of "magic" WSL does with the file system. Even though it is installed on windows NFTS could WSL presenting the file system differently. In the link you sent it says:
"It will not work on any filesystem formatted in NTFS or ex/FAT/32. It will not work in WSL (Windows Subsystem for Linux) when using a mounted host directory (commonly under /mnt). "
I am not using a mounted filesystem for the PG database.
Frankly, all of this virtualization confuses me. But, withon the docker container the PG data is stored at /var/lib/postgresql/data.
Those docs specifically say to use a docker volume instead
You haven't done that
The file system inside WSL (WSL is just a VM) is EXT4
I think I understand. So, it says "If this is an issue, you can change the bind mount to a Docker volume." I did read that during the install but since it seemed to work as is I did not do this.
So, I need to create a docker volume (called pgdata to fit the instructions?) and then alter the .env and docker-compose files to match. Correct? I am very much a docker newbie, so I will search for how to create a volume. Thanks for your patience. 🙂
So, I need to create a docker volume (called pgdata to fit the instructions?) and then alter the .env and docker-compose files to match. Correct? I am very much a docker newbie, so I will search for how to create a volume. Thanks for your patience. 🙂
If this is an issue, you can change the bind mount to a Docker volume.No. It's an "If you're using windows, do this. It will break" But yeah, the steps sound correct :)
thank you. your verbage is much more clear. Is there any hope I can move the database over to the volume or should I just recreate everything from the start and then use immich-go to import the data?
You can try a database dump and restore that. If that works you're probably good
Actually, I think it was not correct of me to say that the database was on NTSF. It was stored within WSL 2 so it was stored on an EXT4 filesystem. Possibly PG does not work well with WSL 2, although I have a well working nextcloud which uses PG. In any case, I shall try to create a seperate docker volume for the database and see if that helps.
The folder you were in most likely was a mapped windows folder
Just to add closure to this. The problem had nothing to do with the database or the underlying filesystem. I had installed immich directly onto WSL 2 Ubuntu with success. In the process I installed docker packages. I also had Docker Desktop installed on the windows 11 machine with underlying WSL 2 support. I did not realize that seemed to result in two docker system on the WSL Ubuntu. It seemed to be OK for a week until the docker desktop upgraded. At that point it caused a problem. I noticed that even though all of my immich containers were down, docker was still listening on the immich port (lsof -i :2283). Google-ing revealed that this can be caused by 2 docker engines running. I removed all docker packages on Ubuntu and re-initialized (turned off and then back on) the docker desktop WSL 2 integration. After that, I brought up the immich containers and all works.