Nomad v0.7.1 (0b295d399d00199cfab4621566babd25987ba06e)
Ubuntu Xenial on AMD64.
I’m using ACLs.
I’m trying to access the Web UI but on every server and client except for the leader, the UI flashes shortly and then I get a
Server Error
A server error prevented data from being sent to the client.

error message before being able to enter a token. I’ve tried Safari, Chrome, and Firefox.
The browser console looks like this:

The only relevant log messages on the server side is these two:
Dec 28 19:48:03 c-0175 nomad-server[232]: 2017/12/28 19:48:03.879031 [ERR] http: Request /v1/nodes, error: rpc error: Permission denied
Dec 28 19:48:03 c-0175 nomad-server[232]: 2017/12/28 19:48:03.879388 [DEBUG] http: Request /v1/nodes (1.565328ms)
Dec 28 19:48:03 c-0175 nomad-server[232]: 2017/12/28 19:48:03.879815 [ERR] http: Request /v1/agent/members, error: Permission denied
Dec 28 19:48:03 c-0175 nomad-server[232]: 2017/12/28 19:48:03.880152 [DEBUG] http: Request /v1/agent/members (472.674µs)
It’s unfortunate because I would like to use https://nomad.service.consul:4646 as the canonical URL (AFAIK, it’s impossible to determine the leader using a tag like with Vault?).
Interestingly, the API works just fine – I’m not getting any errors when using the nomad CLI client with NOMAD_ADDR set to https://nomad.service.consul:4646
Is this behaviour intended or documented? I don’t seem to be able to find anything on Google or GitHub which is deeply confusing me.
FTR, a successful request looks like this:

in the browser.
We've ran into the same issue. Interestingly enough, injecting a proper X-Nomad-Token header actually "fixes" the error.
P.S.: We didn't modify the anonymous user's permissions so it cannot see anything. Maybe when it has some access this issue won't show up? Not sure about that though.
I can confirm, that ui works fine when anonymous user is allowed to read everything .
Thanks for the bug report @hynek! PR is up and will be in the next release. No easy workaround in the meantime unfortunately.
Most helpful comment
Thanks for the bug report @hynek! PR is up and will be in the next release. No easy workaround in the meantime unfortunately.