doc: remote-bitcoind: allowing external connections when tor.enforce is active

This commit is contained in:
Otto Sabart 2022-06-27 21:38:00 +02:00
parent 1ba7ccc547
commit 8cac828534
No known key found for this signature in database
GPG Key ID: 823BAE99F8BE1E3C

View File

@ -214,6 +214,21 @@ services.bitcoind = {
}; };
``` ```
If a `secure-node.nix` or `tor-enable.nix` preset is imported in your
configuration or a `tor.enforce` option is explicitly enabled, you also need to
allow remote connections for **every** service which needs to connect to the
remote bitcoind:
```
systemd.services.<service>.serviceConfig = {
IPAddressAllow = [ ${services.bitcoind.rpc.address} ];
};
```
> Please note that configuration above applies only if the remote bitcoind **is
> not** accessed via Tor.
Now save the password of the RPC user to the following files on your nix-bitcoin node: Now save the password of the RPC user to the following files on your nix-bitcoin node:
```shell ```shell
$secretsDir/bitcoin-rpcpassword-privileged $secretsDir/bitcoin-rpcpassword-privileged