-
Notifications
You must be signed in to change notification settings - Fork 3
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
tezos: HTTP status 401 #31
Comments
This is likely caused by the ACLs introduced in one of the latest version of Octez. You need to add the requested endpoints to an allow-list or you can add the You can find more info in the official docs here https://tezos.gitlab.io/user/node-configuration.html?highlight=allow%20all%20rpc#access-control-lists |
Hello, thanks @danielelisi for your answer. as you can see here :
and both I might be missing something obvious, but I'm not sure what :-/ |
Which Octez version are you running on mainnet? Can you try specifying the bind address as |
all my octez nodes (mainnet, granadanet, hangzhounet) are running with |
adding the
makes the following logs in tezos-node-exporter
|
Hello, could it be linked to https://gitlab.com/tezos/tezos/-/issues/2229 ? |
Hello,
the tezos-node exporter is currently failing on both testnets
mainnet : healthy but 401 errors
with the following logs
Granadanet KO
with the following logs
Hangzhounet KO
hangzhounet_tezos-node-exporter_1 /usr/bin/tezos_exporter -- ... Up (unhealthy) 0.0.0.0:9491->9489/tcp,:::9491->9489/tcp
in
with the following logs
config used
docker image
image: ecadlabs/tezos_exporter:v0.0.1-beta.14
as defined in umami-stack-orchestration : https://gitlab.com/nomadic-labs/umami-wallet/umami-stack-orchestration/-/blob/main/umami-stack-compose/docker-compose.yml
If you have any recommendations as to what modify in the docker-compose orchestration to make sure it works correctly, feel free to suggest them !
Thanks in advance for your help !
The text was updated successfully, but these errors were encountered: