-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Authentication Logs not working on Portainer-EE behind reverse proxy #7120
Comments
This still happens in Portainer EE 2.14.0 : I updated the ticket |
Fix for this issue is not in 2.14.0, slated for the next release. |
Thank you for the answer @samdulam ! |
I've been trying a similar configuration with strippath, too, in 2.14.1. Auth logs fail for me the same way. It triggers the basic-auth I have on In addition, If I try to click "Helm" in the sidebar it fails in the same way, as an API call goes to I'm guessing this is an unsupported configuration, but it's a shame almost all of the API calls work just fine in this configuration but these two don't. It might be worth looking for similar occurrences of |
Closing this issue as we already completed the fixed and that will go into Portainer EE 2.15 release. Thanks. |
Bug description
"Authentication Logs" don't work if your Portainer-EE is behind a reverse proxy that serves portainer in a subfolder.
e.g. https://my.host.com/portainer/
The reason is that the path is absolute (
/api/
) instead of relative (api/
)Expected behavior
"Authentication Logs" works.
Portainer Logs
Steps to reproduce the issue:
Technical details:
docker run -p 9443:9443 portainer/portainer
):Additional context
The text was updated successfully, but these errors were encountered: