I'm running a pruned node Bitcoin Core 23.0 gui (on Windows 10). My mission is to run the node through tor (0.4.7.11) for privacy. I'm mostly following this guide ( https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service ).
Basically the steps have been adding the tor as a windows service:
tor.exe --service install -options -f "D:\Path\To\Tor\Folder\torrc"
where torrc has these lines:
ControlPort 9051 CookieAuthentication 1
Okay then I'm trying to change the bitcoin-settings to use tor, these are my lines inside bitcoin.conf:
proxy=127.0.0.1:9050 listen=1 bind=127.0.0.1 onlynet=onion debug=tor
Bitcon Core starts and verifies old blocks but it seems to stop where it should start downloading the new blocks from peers/connections.
Bitcoin debug.log has many lines for example these seem to be connected to tor, "loadblk thread exit" is the last line usually:
torcontrol thread start Bound to 127.0.0.1:8333 Bound to 127.0.0.1:8334 tor: Reading cached private key from D:\xxx\bitcoincore\blockchain\onion_v3_private_key Loaded 0 addresses from "anchors.dat" tor: Successfully connected! tor: Connected to Tor version 0.4.7.11 tor: Supported authentication method: COOKIE tor: Supported authentication method: SAFECOOKIE tor: Using SAFECOOKIE authentication, reading cookie authentication from D:\Windows\System32\config\systemprofile\AppData\Roaming\tor\control_auth_cookie 0 block-relay-only anchors will be tried for connections. tor: Authentication cookie D:\Windows\System32\config\systemprofile\AppData\Roaming\tor\control_auth_cookie could not be opened (check permissions) init message: Starting network threads… ... loadblk thread exit
I guess the problem may be with the Authentication Cookie and permissions because of the "could not be opened (check permissions)", not sure if the permission problem is with tor.exe or with the Bitcoin Core?