Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forward auth with OIDC ends up redirecting to internal ip instead of fqdn #11984

Open
cantchooseaname8 opened this issue Nov 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@cantchooseaname8
Copy link

I set up authentik to be used in front of my Mealie app. If I don't use forward auth then I am taken directly to the mealie login (mealie.domain.com/login). Logging in with Authentic via OIDC works fine in this case.

Then I add the forward auth and insert the provided snippet into Nginx proxy manager's advanced section. Now starting with the same mealie.domain.com, it properly directs me to Authentik first. Once I log into Authentik, it directs me back to the mealie login page. Now when I click the sign in with Authentik option, it redirects to the internal ip 192.168.x.x. External users obviously can't reached that.

If the OIDC works properly, why does it break when adding forward auth? I've been pulling my hair out trying to have it properly redirect to the FQDN but it insists on using the internal ip whenever forward auth and OIDC are being used.

@cantchooseaname8 cantchooseaname8 added the bug Something isn't working label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant