Error with rpcuser and password while trying to run node.

[nerviosus]

I am trying to set up a node on my raspberry pi following this tutorial (https://stadicus.github.io/RaspiBolt/raspibolt_30_bitcoin.html) and almost at the end it gives me an error.
Whenever I try to run 'bitcoin-cli getblockchaininfo', 'bitcoin-cli getblockcount', 'bitcoin'cli getnetworkinfo', etc... It tells me 'Authorization failed: Incorrect rpcuser or rpcpassword'
So I go to the bitcoin.conf file and my rpcuser and rpcpassword is already set and ready to go.

Can somebody help me with this issue?
Thanks.

[1714053469]

1714053469

[1714053469]

1714053469

[AdolfinWolf]

...Authorize with:

Code:

rpcuser=raspibolt
rpcpassword=PASSWORD_[B]

As defined in: https://stadicus.github.io/RaspiBolt/raspibolt_30_bitcoin.html#configuration

What am i missing

Or do it like this? https://bitcoin.stackexchange.com/questions/35454/bitcoin-cli-fails-with-auth-error
Ex https://bitcoin.stackexchange.com/a/74109

[nerviosus]

That's what I have in my config file:
rpcuser:[the name of my node]
rpcpassword:[a new password I specifically set up for this]

How can be incorrect when there's nothing else to compare it to?

[AdolfinWolf]

That's what I have in my config file:
rpcuser:[the name of my node]
rpcpassword:[a new password I specifically set up for this]

How can be incorrect when there's nothing else to compare it to?

You need to pass those arguments in the command line to authorize


Edit

Or does it automatically authenticate like mocca suggested? SE might be outdated. In that case, disregard my posts and see moccas suggestions.

Read a bit more online and i don’t think calling -rpcuser & pass (rpcauth) is depreciated? Might be bad practice though, (&nd useless, i’m not awake yet.)

[nerviosus]

Not in the command line, I have to write them down in the file bitcoin.conf

[mocacinno]

if you run bitcoin-cli as the same user that's running bitcoind, and the config file is in the home ~/.bitcoin of that exact user, bitcoin-cli will also parse bitcoin.conf and automatically authenticate.

My first guesses would be:
- is the same user running bitcoind and bitcoin-cli?
- is there something else wrong with your configuration (is your daemon listening for connections?)
- maybe there's something wrong with the owner or permission of your bitcoin.conf?