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 NPM gives Error 500 in firefox, wrong proxy_set_header config/documentation may be the problem #12911

Open
MrSliff opened this issue Feb 1, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@MrSliff
Copy link

MrSliff commented Feb 1, 2025

Describe the bug
Authentik forward auth with internal outpost and nginx(-proxy-manager) gives me an Error 500 when i try to open my protected sites in Firefox. MS Edge works without errors.

To Reproduce
Steps to reproduce the behavior:

  1. Set up forward-auth as desribed in the tutorials
  2. Add the NginxProxyManager config to the "Advanced" Tab, edit proxy_pass in /outpost.goauthentik.io accordingly
  3. Try to open website -> keeps loading and returns Error 500 after some time

Expected behavior
Website redirects to Authentik and start the authentication process.

Version and Deployment (please complete the following information):

  • authentik version: [e.g. 2024-12-3]
  • Deployment: docker-compose

Additional context

It seems the internal and external documentation is still incorrect. According to #2594, the documentation for NPM inside of authentik and also on the authentik homepage tutorials may be still incorrect.

Both show proxy_set_header Host $host; for the /outpost.goauthentik.io block.

I set the header to proxy_set_header X-Forwarded-Host $host; and now it is working without errors.

@MrSliff MrSliff added the bug Something isn't working label Feb 1, 2025
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