Immich Authelia OAuth Issue
Hey all, love the app so far. I have been trying to get Immich setup with Authelia (for O Auth) and Traefik as my proxy to no avail. Was hoping to get some help. All running as docker containers. When I click the Login with OAuth button I get a server error.
The error in the Immich Server project is Internal Server error. When I check the logs I see the getaddr error.
So seems like it's a dns issue, because if I navigate to that URL in the error, I get an authelia login screen. I am assuming something is wrong with one of my configs at this point.
Attached are my authelia.yml and immich stack yml.
Any help would be appreciated as this is all pretty new to me
11 Replies
Is authelia running on the same host? If so, I would assume you can't ping your authelia instance from the host either, correct?
Oh and also: Where is your dns server running? Same host, docker as well?
Authelia, traefik, and immich are all running on the same docker instance and all sharing that "proxy" network referenced int he immich yml. If I ping from the immich server the ip address of the authelia container, I get a response. When I try and ping the dns name of the container though, I get "name or service not known"
DNS server is adguard, it runs on the a different machine using docker as well.
Does your host has the correct DNS settings? So does it use your adguard server in the first place?
Did you try to add
extra_hosts in your docker-compose ?
This would basically override the adguard server, I don't know if this is desired
@Daniel just made me look and see the issue I think. The proxy network was inheriting my DNS config from the lxc container. Which was not pointing to the correct address. I just updated the immich docker compose and manually added the DNS entry. Clicked the Oauth button on the login page and authelia came right up
Perfect, yay! 👍
Appreciate it! This community is fantastic!
I'm pretty new to Immich myself and I agree... The people running this project are awesome!
It's needed if the server does not use adguard
Yeah, but I would've guessed that the actual issue was that the server isn't using adguard. So that it actually should use the adguard dns