<p>I have my full node connected through Tor. I ended up changing my onion service and now I'm getting <code>error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set.  See -rpcpassword and -stdinrpcpass.  Configuration file: (/home/ubuntu/.bitcoin/bitcoin.conf)</code></p>
<p>So I open up my bitcoin.conf, there was no rpc password or user name set to begin with and added one in so my .conf looks like the following.</p>
<pre><code>prune=15000
proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
externalip=BLANK.onion
rpcuser=me
rpcpassword=mypassword
</code></pre>
<p>Which results in the following:</p>
<pre><code>./bitcoin-cli listdescriptors 
error: Authorization failed: Incorrect rpcuser or rpcpassword
</code></pre>
<p>I also tried passing the -rpcuser and -rpcpassword directly without any luck.</p>
<p>I basically want to backup my wallets descriptors to Sparrow wallet since Electrum currently does not accept descriptors yet.</p>
<p>Any ideas on how to fix?</p>

CC BY-SA 4.0
2022-12-27T17:37:04.407Z
Did you restart Bitcoin Core after modifying the bitcoin.conf file?
Ava Chow
CC BY-SA 4.0
2022-12-28T06:31:43.580Z
results in either error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set.  See -rpcpassword and -stdinrpcpass.  Configuration file: (/home/ubuntu/.bitcoin/bitcoin.conf)

or 

error: Authorization failed: Incorrect rpcuser or rpcpassword 

upon adding or removing rpcuser and rpcpassword
bitcronny
CC BY-SA 4.0
2022-12-28T15:20:56.447Z
You need to restart `bitcoind`; not just `bitcoin-cli`.
Pieter Wuille
CC BY-SA 4.0
2022-12-30T01:26:09.133Z
./bitcoind stop
Error: Command line contains unexpected token 'stop', see bitcoind -h for a list of options.



https://bitcoin.stackexchange.com/questions/13696/how-to-safely-shutdown-bitcoind
bitcronny
CC BY-SA 4.0
2022-12-30T01:32:48.157Z
Just use `killall bitcoind` to stop it. You can't use bitcoin-cli to send the stop command, as that needs bitcoin-cli, which doesn't work.
Pieter Wuille
<bitcoin-core><bitcoin-cli>
Bitcoin core V22 Authorization failed: Incorrect rpcuser or rpcpassword
bitcronny
# Bitcoin core V22 Authorization failed: Incorrect rpcuser or rpcpassword

(Asked by: username_0 on 2022-12-27)

I have my full node connected through Tor. I ended up changing my onion service and now I'm getting `error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set. See -rpcpassword and -stdinrpcpass. Configuration file: (/home/ubuntu/.bitcoin/bitcoin.conf)`

So I open up my bitcoin.conf, there was no rpc password or user name set to begin with and added one in so my .conf looks like the following.

```
prune=15000
proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
externalip=BLANK.onion
rpcuser=me
rpcpassword=mypassword

```

Which results in the following:

```
./bitcoin-cli listdescriptors 
error: Authorization failed: Incorrect rpcuser or rpcpassword

```

I also tried passing the -rpcuser and -rpcpassword directly without any luck.

I basically want to backup my wallets descriptors to Sparrow wallet since Electrum currently does not accept descriptors yet.

Any ideas on how to fix?

**Tags:** bitcoin-core, bitcoin-cli

> **Comments:**
> **username_1**: Did you restart Bitcoin Core after modifying the bitcoin.conf file?  
> **username_0**: results in either error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set.  See -rpcpassword and -stdinrpcpass.  Configuration file: (/home/ubuntu/.bitcoin/bitcoin.conf)  or   error: Authorization failed: Incorrect rpcuser or rpcpassword   upon adding or removing rpcuser and rpcpassword  
> **username_2**: You need to restart `bitcoind`; not just `bitcoin-cli`.  
> **username_0**: ./bitcoind stop Error: Command line contains unexpected token 'stop', see bitcoind -h for a list of options.    https://bitcoin.stackexchange.com/questions/13696/how-to-safely-shutdown-bitcoind  
> **username_2**: Just use `killall bitcoind` to stop it. You can't use bitcoin-cli to send the stop command, as that needs bitcoin-cli, which doesn't work.  

---

## 0 answers

