bug: "result": "RPC client error: sendRequest failed: http status 401 Unauthorized unmarshaling response: EOF" on querying account-address

[jcstein]

Celestia Node version

v0.13.5

OS

macOS

Install tools

docs

Others

No response

Steps to reproduce it

1. run a light node with state access using celestia light start --p2p.network arabica --core.ip validator-1.celestia-arabica-11.com
2. try to query the account address with celestia state account-address --node.store $HOME/.celestia-light-arabica-11
3. receive result:

{
  "result": "RPC client error: sendRequest failed: http status 401 Unauthorized unmarshaling response: EOF"
}

Expected result

account address

Actual result

http status 401 Unauthorized unmarshaling response: EOF

Relevant log output

No response

Notes

No response

[distractedm1nd]

I'm assuming this is fixed by this pr and #3385 can fix it once released.

Expected Result should probably not be "account address", 401 signifies you did not have permission to access that endpoint -- meaning the expected result should be an error and not a result, with a cleaner ouput.

The 401 could either be internally from node/jsonrpc (by not setting the auth token), or from your networking setup between the client and node. Could you provide more details from the setup?

[jcstein]

my setup is just me running celestia light start --p2p.network arabica --core.ip validator-1.celestia-arabica-11.com in one terminal, and in another, trying to get the account address celestia state account-address --node.store $HOME/.celestia-light-arabica-11

it also fails if i provide the auth token by doing:

export CELESTIA_NODE_AUTH_TOKEN=$(celestia light auth write --p2p.network arabica)
celestia state account-address --token $CELESTIA_NODE_AUTH_TOKEN

[jcstein]

here is a loom

[jcstein]

hold on a second...i think the auth token needs to be admin not write, but i guess there is still a bug in here as i should receive a more useful and readable error

export CELESTIA_NODE_AUTH_TOKEN=$(celestia light auth admin --p2p.network arabica)
celestia state account-address --token $CELESTIA_NODE_AUTH_TOKEN
{
  "result": "celestia1lvns26q9d43a5fcl3xjmfy3auk6fekf2x5pp93"
}

[Wondertan]

hold on a second...i think the auth token needs to be admin not write, but i guess there is still a bug in here as i should receive a more useful and readable error

Hmn, the logic added by @mastergaurang94 that removes the need to specify the store should have automatically gotten the admin token. Do i understand correctly that you don't have this issue when you specify admin token, but when not it fails?

[jcstein]

@Wondertan #3246 is not included in v0.13.5 release

if running:

1. the nodecelestia light start --p2p.network arabica --core.ip validator-1.celestia-arabica-11.com
2. then requesting account address with no auth token or node store, it errors because it needs either auth or node store, as expected.

celestia state account-address
Error: cant get the access to the auth token: token/node-store flag was not specified
Usage:
  celestia state account-address [flags]

Flags:
  -h, --help   help for account-address

Global Flags:
      --node.store string   The path to root/home directory of your Celestia Node Store
      --token string        Authorization token
      --url string          Request URL (default "http://localhost:26658")

[Wondertan]

Ah, I see, thanks for correction

[jcstein]

and now that i've changed the auth token to admin, i cannot reproduce an error where:

celestia state account-address --node.store $HOME/.celestia-light-arabica-11

results in an error. i don't know how this is related, though tbh 😅

i can also use this successfully and see no error from using write instead of admin

export CELESTIA_NODE_AUTH_TOKEN=$(celestia light auth write --p2p.network arabica)
celestia state account-address --token $CELESTIA_NODE_AUTH_TOKEN
{
  "result": "celestia1lvns26q9d43a5fcl3xjmfy3auk6fekf2x5pp93"
}

[renaynay]

@jcstein Is the issue resolved here? If so, feel free to close the issue

[jcstein]

yep let's close this