Skip to content

Commit 7063401

Browse files
clashiclyclashic
authored andcommitted
Elaborate on the need to re-login on Debian-based systems to use tor following usermod
Starting bitcoind with `-onlynet=onion` immediately after adding bitcoind user to debian-tor group will yield the following notice on debug.log: "tor: Authentication cookie /run/tor/control.authcookie could not be opened (check permissions)" Elaborate on the need to re-login to ensure debian-tor group has been applied to bitcoind user after: sudo usermod -a -G debian-tor username Verification can be done via `groups` command in shell.
1 parent 2324aa1 commit 7063401

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

doc/tor.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,10 @@ preconfigured and the creation of a hidden service is automatic. If permission p
114114
are seen with `-debug=tor` they can be resolved by adding both the user running Tor and
115115
the user running bitcoind to the same group and setting permissions appropriately. On
116116
Debian-based systems the user running bitcoind can be added to the debian-tor group,
117-
which has the appropriate permissions.
117+
which has the appropriate permissions. Before starting bitcoind you will need to re-login
118+
to allow debian-tor group to be applied. Otherwise you will see the following notice: "tor:
119+
Authentication cookie /run/tor/control.authcookie could not be opened (check permissions)"
120+
on debug.log.
118121

119122
An alternative authentication method is the use
120123
of the `-torpassword=password` option. The `password` is the clear text form that

0 commit comments

Comments
 (0)