Fixing CORS in Nginx for statistics in Homer dashboard
Hi. I am getting CORS issues with Homer dashboard + Immich. In my setup Immich is behind Swag (based on. Nginx). Usually I fix this by adding
add_header Access-Control-Allow-Origin *; in the Nginx location of the proxied service. In this case the destination is https://immich.example.com/api/server/statistics. I added the usual line in the location /api/server/statistics { block (or also location ~ (/immich)?/api, like mentioned in https://github.com/linuxserver/reverse-proxy-confs/blob/8625ed9dbd0ae9aab4d64ac571d1c4403533ab74/immich.subdomain.conf.sample#L48), but it doesn't have effect. Do you have any idea why?4 Replies
:wave: Hey @elmuz,
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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :ballot_box_with_check: 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. :ballot_box_with_check: 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.We have a simple nginx example that covers basically everything:
https://immich.app/docs/administration/reverse-proxy/#nginx-example-config
If it doesn't work with the simple config then something must be misconfigured elsewhere 🙂
Not really. I feel there's something missing on the CORS side. In particular, something on the realm of the preflight. This approach (https://github.com/bastienwirtz/homer/issues/396#issuecomment-1612418113) kind of solved for me, but I am not expert enough to comment further. I can tell you that for most services this customization is not required (I mean the "if section") this is why I was thinking that it can be addressed in Immich.
If you think this is not relevant we can close this.
As far as I know immich doesn’t set any headers like this, CORS or otherwise. This will be a proxy issue