<p>In case you changed your <code>/etc/systemd/system/bitcoind.service</code> make sure you run</p>
<pre><code> sudo systemctl stop bitcoind
 sudo systemctl daemon-reload
 sudo systemctl start bitcoind
</code></pre>
<p>to apply the changes.</p>

CC BY-SA 4.0
2020-11-15T23:19:50.783Z
While this advice may be useful, the question doesn't ask anything about systemd or with changing systemd service files.
Ava Chow
CC BY-SA 4.0
2020-11-06T21:13:48.950Z
2020-11-06T21:13:48.950Z
bomben
<p>After installing bitcoin on CentOS/AWS, an error occurs when connecting with cli.</p>

<pre><code>$ bitcoind -daemon -conf=/.bitcoin/bitcoin.conf
Bitcoin server starting
$ bitcoin-cli getbalance
error: Authorization failed: Incorrect rpcuser or rpcpassword
</code></pre>

<p>The following is bitcoin.conf.</p>

<pre><code>mainnet = 1
txindex = 1
server = 1
rest = 1
rpcuser = a
rpcpassword = a
rpcport = 8332
</code></pre>

CC BY-SA 4.0
2019-03-29T11:00:01.420Z
The following is displayed when executing bitcoind.
----------
Binding RPC on address ::1 port 8332 failed.
----------
Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
----------
kotora
CC BY-SA 4.0
2019-03-29T16:21:08.930Z
`-conf=/.bitcoin/bitcoin.conf` is unusual as it suggests you're keeping the `.bitcoin` outside your `/home` folder. If that's a mistake, it would explain why bitcoin-cli can't find the credentials - the conf file you're specifying doesn't exist. Are you sure you sure you don't mean `-conf=/home/<user>/.bitcoin/bitcoin.conf`?
Alistair Mann
CC BY-SA 4.0
2019-04-01T12:43:21.883Z
Thank you for answering.I created bitcoin.conf with the following command. Is that wrong?
mkdir ~/.bitcoin
vi ~/.bitcoin/bitcoin.conf
kotora
CC BY-SA 4.0
2019-04-09T10:41:55.157Z
If that's two commands then they do seem right. However your question says you used `/.bitcoin/bitcoin.conf` which is not the same as `~/.bitcoin/bitcoin.conf`. The first says start in the root of your file system, the second - with a tilde '~' - says to start in your home folder.
Alistair Mann
<installation>
error: Authorization failed: Incorrect rpcuser or rpcpassword
kotora
# error: Authorization failed: Incorrect rpcuser or rpcpassword

(Asked by: username_0 on 2019-03-29)

After installing bitcoin on CentOS/AWS, an error occurs when connecting with cli.

```
$ bitcoind -daemon -conf=/.bitcoin/bitcoin.conf
Bitcoin server starting
$ bitcoin-cli getbalance
error: Authorization failed: Incorrect rpcuser or rpcpassword

```

The following is bitcoin.conf.

```
mainnet = 1
txindex = 1
server = 1
rest = 1
rpcuser = a
rpcpassword = a
rpcport = 8332

```

**Tags:** installation

> **Comments:**
> **username_0**: The following is displayed when executing bitcoind. ---------- Binding RPC on address ::1 port 8332 failed. ---------- Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. ----------  
> **username_1**: `-conf=/.bitcoin/bitcoin.conf` is unusual as it suggests you're keeping the `.bitcoin` outside your `/home` folder. If that's a mistake, it would explain why bitcoin-cli can't find the credentials - the conf file you're specifying doesn't exist. Are you sure you sure you don't mean `-conf=/home/<user>/.bitcoin/bitcoin.conf`?  
> **username_0**: Thank you for answering.I created bitcoin.conf with the following command. Is that wrong? mkdir ~/.bitcoin vi ~/.bitcoin/bitcoin.conf  
> **username_1**: If that's two commands then they do seem right. However your question says you used `/.bitcoin/bitcoin.conf` which is not the same as `~/.bitcoin/bitcoin.conf`. The first says start in the root of your file system, the second - with a tilde '~' - says to start in your home folder.  

---

## 1 answers

### Answer by username_2 on 2020-11-06. Score: -1

In case you changed your `/etc/systemd/system/bitcoind.service` make sure you run

```
 sudo systemctl stop bitcoind
 sudo systemctl daemon-reload
 sudo systemctl start bitcoind

```

to apply the changes.

> **Comments:**
> **username_3**: While this advice may be useful, the question doesn't ask anything about systemd or with changing systemd service files.  

---

