Strange error
I updated my docker stack this morning and I got the error noted in the screenshot. Any idea how to fix this? Everything was running fine until a few days ago.
12 Replies
:wave: Hey @Rick,
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.Sorry, this is my first time on this discord. I don't understand how to respond to most of this. There are 4 different containers; which do you want logs for? All containers are green/healthy. I can reach immich directly on my lan, but not via the reverse proxy, and therefore the mobile app can't reach my server. I am on the latest release, though the valkey/redis container and the postgres containers show that they are out of date. I simply re-pulled and deployed the stack, as with any/most docker image updates
What screenshot?
docker compose logs will include logs for all containers
If all containers are healthy and you can reach it over lan it's a proxy issue
Most likely you have to clear cache somewhereThe original message wouldn't post with the error message copy and pasted, so I added a screenshot, which obviously didn't get sent. The error is this: Error: 502 - undefined
Error: Error: 502
at Object.st [as ok] (https://immich.3stradastone.com/_app/immutable/chunks/BlM8hC-9.js:1:5407)
at async Promise.all (index 0)
at async c (https://immich.3stradastone.com/_app/immutable/chunks/Bi5Wdvtn.js:1:524)
at async o (https://immich.3stradastone.com/_app/immutable/chunks/CLWHzq40.js:1:177) docker compose logs does nothing. Do you want me to copy and paste the logs from each of the 4 containers? Sorry, but this is my first time posting here and this seems a bit unclear
The only container with errors in the log is the postgres container. Both postgres and redis are out of date, but I don't understand how to update to the correct version. I spun up the official docker yaml originally and everything was fine
As @ Mraedis pointed out, it's related to
reverse proxy -> Immich communication
You get 502 Bad Gateway from reverse proxy, most likely it cannot reach Immich. Maybe Immich IP address has changed after the update (if you confingured proxying by IP).
Check the reverse proxy config.Thanks for responding. I have my NPM proxies set up pointing to container names rather than IP addresses. The container name is still the same, as well as the port. Did something change with this update that would require different settings in NPM?
No, immich has no hand in this
That seems unlikely as nothing changed on my servers outside of the recent update, but thanks. However, I notice that there are two of the four containers that seem to be out of date, based on the named images that were set up as part of the original deployment from the official docker compose. Where can I find information about the safety of updating either of these (valkey and postgres)? Or do I need to be concerned at all?
You shouldn't concern yourself with these images as they get frequent minor updates that do not affect immich at all, so they will almost always show as out of date
Are you caching in NPM?
Are you caching in your browser?
Try a different browser or a private window
I hadn't added the npm network settings into my compose file yet. But glad I was able to get an answer about valkey and postgres images. Thanks for the help. Much appreciated
Cool that you resolved it.
Have you considered placing custom compose stuff into override.yml? To simplify upgrades: just swap main compose with the file from newer version.
In my setup
docker-compose.yml is the stock one. Customization done through docker-compose.override.yml and .env. Networking part from override for example:
I only started working with docker a couple of months ago. I did realize exactly what you're saying, and I thought I had included that text in every stack's yaml file, but obviously I missed that one. Thanks for the reminder!