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
Redirection Not Working #364
Comments
Hello @n4kre , long time no see :). There is nothing obvious that I can spot in the config. Can I see some logs? |
The |
Don't hesitate to contribute in the documentation with all security related headers that you're using. That could really be helpful to others. |
When I'll be sure that my Nginx configuration is not at fault, I will. :) For the redirection, there is unfortunately not much to see on server side, since the URL fragment (the URL part starting with Here is an excerpt of Authelia's logs:
Meanwhile, this is where I'm stuck (and I can't see any error in the web browser console): |
As suggested by line
I don't see any request to the server so that the latter knows where to redirect the user: (It's only GET requests, so the redirection parameter should be visible in requested URLs, if any.) |
I got stucked like this as well. Any suggestion, how to debug? |
This issue seems no longer suitable for latest version, since the redirection parameter is changed to |
@clems4ever Seems this issue is no longer valid since the configuration changed a few times, and this issue is stalled. Maybe you can consider to close this one? |
@mqmq0's issue was related to his nginx config. |
Hi @clems4ever,
Coming from early versions of Authelia, I'm glad to experiment version 3.15.0! It looks really cool – thanks for your effort. :)
However, I can't get the redirection working anymore, although I updated my Nginx configuration based on the documented example.
When I visit
https://private.example.com/
(unauthenticated), I get redirected tohttps://login.example.com/#/?rd=https://private.example.com/
(note that I have/#/?rd=
and not/?rd=
), but then the redirection does not occur upon successful authentication.Any clue on what could go wrong?
For your reference, I am using the following Nginx configuration.
Content of
/etc/nginx/sites-enabled/login.example.com
– assuming Authelia runs athttp://127.0.0.1:4221
:Content of
/etc/nginx/sites-enabled/private.example.com
– assuming protected backend runs athttp://127.0.0.1:8000
:Content of
/etc/nginx/authelia_check-auth_block_internal_api
:Content of
/etc/nginx/authelia_sso_params
:Content of
/etc/nginx/default_headers
:Content of
/etc/nginx/default_headers_no-cache
is the same as/etc/nginx/default_headers
, with the following extra lines:Content of
/etc/nginx/proxy_params
:The text was updated successfully, but these errors were encountered: