-
Notifications
You must be signed in to change notification settings - Fork 38.7k
Closed
Description
Add onion failed; error code 513
Details mentioned in debug.log:
2021-02-10T20:01:58Z tor: Successfully connected!
2021-02-10T20:01:58Z tor: Connected to Tor version 0.3.2.10
2021-02-10T20:01:58Z tor: Supported authentication method: COOKIE
2021-02-10T20:01:58Z tor: Supported authentication method: HASHEDPASSWORD
2021-02-10T20:01:58Z tor: Supported authentication method: SAFECOOKIE
2021-02-10T20:01:58Z tor: Using SAFECOOKIE authentication, reading cookie authentication from /var/run/tor/control.authcookie
2021-02-10T20:01:58Z tor: SAFECOOKIE authentication challenge successful
2021-02-10T20:01:58Z tor: AUTHCHALLENGE ServerHash fec05d578a7f60d426bc9fbee942102f458f3921db4585c5020d3295b58c56d1 ServerNonce eb57b69b846cfa0984905079b964b0662d71c134cc0afd816cb297d24d37dc10
2021-02-10T20:01:58Z tor: Authentication successful
2021-02-10T20:01:58Z tor: Add onion failed; error code 513
2021-02-10T20:01:58Z Loaded 19221 addresses from peers.dat 209ms
2021-02-10T20:01:58Z Loaded 2 addresses from "anchors.dat"
2021-02-10T20:01:58Z 2 block-relay-only anchors will be tried for connections.
2021-02-10T20:01:58Z init message: Starting network threads...
2021-02-10T20:01:58Z init message: Done loading
2021-02-10T20:01:58Z msghand thread start
2021-02-10T20:01:58Z opencon thread start
2021-02-10T20:01:58Z addcon thread start
2021-02-10T20:01:58Z dnsseed thread start
Not sure why it connects to Tor version 0.3.2.10 because I have a recent version on this machine:
prayank@ubuntu:~/.bitcoin$ tor --version
Tor version 0.4.4.6.
What can be the possible reason for this error?
bitcoin.conf file:
testnet=1
listen=1
torcontrol=127.0.0.1:9051
onlynet=onion
debug=tor
prune=555
/etc/tor/torrc
ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1
HashedControlPassword 16:07XXXXXXXXXXXXXXXXXXXXXXXXXXXX$
Metadata
Metadata
Assignees
Labels
No labels