You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: