-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
ACL disabled does not equal all features being available #14392
Comments
similar issues - #14359 |
This exact error scenario also applies to the "Exec" functionality, including when the workaround in #14359 is used.
|
My apologies for missing that issue and thanks for all the work! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
1.3.4
Operating system and Environment details
Ubuntu 22.04
Issue
The CPU and Memory Resource Utilization graphs in the UI are empty as well as the logs. When looking through the errors in the browsers console (errors listed below), one error points to
/v1/acl/policy/anonymous
. When the Nomad front end tries to load this endpoint, the endpoint returns a 400 with the text "ACL support disabled". This is correct, I have not enabled ACL. However, according to https://learn.hashicorp.com/tutorials/nomad/web-ui-considerations, "Nomad starts with ACLs disabled by default, which means all features—read and write—are available to all users of the Web UI out of the box". So, this is a contradiction.Reproduction steps
I have a pretty basic setup where the Nomad UI is set up behind a reverse proxy.
Click here to see the task definition
task "caddy" { driver = "docker"Nomad Client logs
This is the error that is shown in the browser developer tools:
This error is shown when a page for an allocation is open.
I've checked the
/v1/acl/policy/anonymous
link by browsing to the page manually and it responds withThe text was updated successfully, but these errors were encountered: