[SOLVED] Cannot GET /api/server-info/config
I'm getting the following error message when trying to login to immich
I just updated to 1.79.1. Not sure why this is happening. All of my pods are running (this is running in k8s). No log output other than the browser errors and I can't connect with the app. Any help would be appreciated.
19 Replies
I still can't access the website anymore. Could it be permission related? What permissions do the image files need to have? I just changed them to uid/gid 1000 from an old permission set
Here is the browser console
Downgrading to 1.79.0 didn't fix it. It must be permission based
setting the photos library to 777 permissions didn't seem to help.
Are you sure the server container is running and working?
This shouldn't be related to library permissions at all
Looks like an issue with your reverse proxy?
I'll take a look again but yes the server is definitely running. I'm using the nginx ingress controller in kubernetes for the proxy.
It could be running but still broken, have you checked the logs?
And can you post your helm values/manifests for immich?
the route is returning a 404 which means the connection is going somewhere, just probably the wrong place. If you click on it or look at it in the network tab, it might be helpful to send the response body/headers here. It usually will indicate what web server handle the request, etc.
I'll do that when I get home. Thanks! I have been looking at the logs and I haven't seen one thing come through.
So here is what I've collected. Basically none of the API calls are working, and the logs aren't showing anything. Unless I'm looking in the wrong area? Top console is the server, bottom console is the web.
are you using immich-proxy or no?
It looks like the response is coming from express, which indicates nodejs is handling it. If you click on the third tab "response", does it have a response body?
I'm guessing you are not using immich-proxy and the
/api part isn't being stripped off of the request to the immich containerI am not using immich proxy. The response just says 404 not found at the api path.
Have a look at https://immich.app/docs/administration/reverse-proxy
Reverse Proxy | Immich
When deploying Immich it is important to understand that a reverse proxy is required in front of the server and web container. The reverse proxy acts as an intermediary between the user and container, forwarding requests to the correct container based on the URL path.
it's best always to use immich-proxy, and if you want additional reverse proxies, put them in front of immich-proxy
So I took a look at my config again. I have based my setup based on several kuernetes@home builds (which I believe @bo0tzz is also a member of). Looking at my configuration compared to several others they appear to all be extremely similar if not identical. You can find my helm release here:
https://github.com/ModestTG/jace-cluster/blob/main/kubernetes/apps/media/immich/app/web/helmrelease.yaml
Based on the reading of the Reverse Proxy page, it looks like my configuration is doing the "Replacing the Default Reverse Proxy" with this snippet in my HelmRelease:
https://github.com/ModestTG/jace-cluster/blob/745ba8395bd9a5b186a4818b9c1c84b0f69afc85/kubernetes/apps/media/immich/app/web/helmrelease.yaml#L61
This seems to be working for others, yet, not for me. I haven't seen any chatter on the K8S@home discord but maybe I missed it? Hopefully this helps.
GitHub
jace-cluster/kubernetes/apps/media/immich/app/web/helmrelease.yaml ...
Contribute to ModestTG/jace-cluster development by creating an account on GitHub.
GitHub
jace-cluster/kubernetes/apps/media/immich/app/web/helmrelease.yaml ...
Contribute to ModestTG/jace-cluster development by creating an account on GitHub.
That does look correct to me, but I don't use this rewrite method myself so I'm not certain. If you want to stick with that, it might be better to open a support thread over in kah? The alternative is using immich-proxy I guess
The rewrite is supposed to be in the location block though
A whole bunch of other people are using the exact same rewrite annotation successfully
Oh @Eazy E I think I may know what's causing you the issue, sec
On the latest ingress-nginx chart, config snippet annotations are disabled by default and you need to allow them by setting
controller.allowSnippetAnnotations: true on the ingress-nginx helmreleaseI'll give that a test when I get home. Thanks for digging and finding that!!
I'm very happy to report that this fixed it. I probably would have never found that change. Thank you very much for your help and patience!