Immich OICD Auth issue #287
Labels
No labels
bug
chore
documentation
enhancement
help
in-progress
question
ready-for-release
released
translation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
adam/gate#287
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi there
I want to secure my immich but get this issuer below.
Describe the bug:
I want to auhenticate Immich with voidauth but I get allways this error in Immich:
I have Portainer successfully configured with oauth and immich/portainer and voidauth are within the same reverseproxy and docker swarm environment.
I tried also the Auth Methods post/basic and none.
The Immich traedfik swarm compose label are
The portainer traedfik swarm compose label are
The main difference is the middleware?
Screenshots:
Voidauth Config
Immich Confg
I tried it now also with the docker compose labels:
Same issue
Interesting, I see in the Immich error message that there is a connection timeout when Immich tries to use the token endpoint (I assume after a successful login/redirect from VoidAuth). I also see that the url in the error is like
voidauth.myDomain.com:80(sanitized?) which I think should just be the token endpoint url of VoidAuth but I don’t know how that is getting set. At the very least I think it should be over https (so port 443). Unfortunately I don’t see anything immediately in your VoidAuth or Immich configs that looks wrong.The proxy stuff shouldn’t matter I don’t think, OIDC endpoints are public URLs otherwise users wouldn’t be able to sign in, and apps should just use those same endpoints to get user tokens and info. I guess you could try and see if you can reach the public VoidAuth URL from within the Immich container, if not then that would be a problem.
I saw that timeout as well an tried the :80 forcefully set to :443 (yes it is sanitized) within the immich config - same error. I tried it with skip consent and got forwarded to voidauth and after giving the consent I do not get redirected to immich, somehow like the this other reported error.
Also I am not so sure that this is the error, earlier I have the error "OAuth login failed: fetch failed" in the fist two lines.
True. Just to clarify, you are getting redirected to VoidAuth to perform a login and once successful, you are not being sent back to Immich or you are but Immich is giving an error when you get back?
I saw that timeout as well an tried the :80 forcefully set to :443 (yes it is sanitized) within the immich config - same error. I tried it with skip consent and got forwarded to voidauth and after giving the consent I do not get redirected to immich, somehow like the
Also I am not so sure that this is the error, earlier I have the error "OAuth login failed: fetch failed" in the fist two lines.
This is the Immich error screen
And here the log:
I have just setup a similar stack Immich (stack from Portainer) and VoidAuth (standalone container) both proxied through Nginx Proxy Manager and have had no issues.
I got it working with the configuration on both VoidAuth and Immich looking exactly like how @sepidre has it in his screenshots except for one difference -> for the Immich ISSUER_URL I did not use the full Well-Known Endpoint but only the OIDC Endpoint. The Immich docs say that the well-known path is not necessary and gets appended. Maybe you can try changing that.
Otherwise that would point at a Traefik / middleware misconfiguration