Reverse Proxy issue
I am running immish on docker latest release. I am using the standard yaml file with no change. I have SWAG using NGINX as reverse proxy. My server works perfectly on the local network . When I access it on the subdomain, I get the below error from immish. So actualy the traffic is routed finally to immich. proxy conf attached. I have read the reverse proxy conf guide.
🚨 Error - Something went wrong
Error: 502 ()
Stacktrace
Error: Error: 502
at Object.ct [as ok] (https://immich.kkodera.duckdns.org/_app/immutable/chunks/CpqwS_fC.js:1:7600)
at async Promise.all (index 1)
at async f (https://immich.kkodera.duckdns.org/_app/immutable/chunks/5ZMBlMfw.js:1:511)
at async o (https://immich.kkodera.duckdns.org/_app/immutable/chunks/C6AWWxEx.js:1:177)
8 Replies
:wave: Hey @Kodera1979,
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.location ~ (/immich)?/api {
Are you trying to run immich on a subpath?
Cause that's not supportedno it is running as subdomain.
immich.DDNS-Domain.org for example
set $upstream_app immich; in the second (API) proxy block
vs
set $upstream_app immich_server; in the first proxy block
So immich vs immich_server - is this expected difference?Then why do you have a location block with subpath?
Agree, the second (subpath) block looks redundant for the subdomain case and maybe misconfigured
Thanks a lot. Once I fixed the second block. All work fine
This was the same issue I had, fixing the second block also worked!