joinmarket-clientserver icon indicating copy to clipboard operation
joinmarket-clientserver copied to clipboard

directory node service hangs then errors out

Open techy2 opened this issue 1 year ago • 3 comments

Setting up directory node service, it is not clear from the abbreviated FAQ how to do this tor and start-dn.py both start tor populates the onion address and that start-dn.py seems to run with this value however it hangs and errors out as follows, nothing abnormal in the tor debug log. This text on the console from start-dn.py debug

2024-12-13 12:26:51,164 [INFO] starting directory node 2024-12-13 12:26:51,165 [INFO] Joinmarket daemon listening on port 27183 2024-12-13 12:26:51,169 [INFO] Attempting to start onion service on port: 5222 ...
Unhandled error in Deferred:

Traceback (most recent call last): --- --- File "/home/michael/joinmarket-clientserver/jmvenv/lib/python3.10/site-packages/txtorcon/endpoints.py", line 651, in listen self.hiddenservice = yield create_d File "/home/michael/joinmarket-clientserver/jmvenv/lib/python3.10/site-packages/txtorcon/onion.py", line 253, in create yield config.save() txtorcon.torcontrolprotocol.TorProtocolError: 513 Unacceptable option value: Failed to configure rendezvous options. See logs for details.

====================================

I think that the configuration values may not be correct, they are below Someone that runs a directory node please review and comment Thanks

tor and joinmarket run on the same debian host host ip address: 11.22.33.44 advise and correct configuration value for 'torrc'

torrc

SocksPort 9050 #SocksPolicy unused, accepts all connections Log notice /var/log/tor/notice.log RunAsDaemon 1 ControlPort 9051 CookieAuthentication 1 CookieAuthFileGroupReadable 1 HiddenServiceDir /var/lib/tor/jm-dm-service HiddenServicePort 5222 127.0.0.1:5222 ExitPolicy reject : # no exits allowed

Any ERRORS or changes needed???

==================================

joinmarket.cfg

[DAEMON] no_daemon = 0 daemon_port = 27183 daemon_host = localhost

[BLOCKCHAIN] blockchain_source = no-blockchain network = mainnet

[MESSAGING:onion] type = onion socks5_host = localhost socks5_port = 9050 tor_control_host = localhost tor_control_port = 9051 onion_serving_host = 127.0.0.1 onion_serving_port = 5222 # is this correct?? hidden_service_dir = /var/lib/tor/jm-dn-service hidden_service_ssl = false directory_nodes = myonionhostnamefromtor.onion:5222 regtest_count = 0,0

[LOGGING] console_log_level = INFO color = true

are these needed??

[TIMEOUT] maker_timeout_sec = 60 unconfirm_timeout_sec = 180 confirm_timeout_hours = 6

techy2 avatar Dec 13 '24 20:12 techy2

better late, then never) The Problem could be that Tor lost underlaying connection (maybe b/c VPN or network cable reconnection), after that, Tor will establish new circuit, so previous registration of your Maker's onion domain will become invalid, and some time required to rebuild onion route(s).

perdidor avatar May 13 '25 14:05 perdidor

add: as far as i understand, directory node requires constant onion domain name, so you need first to create hidden service manually in torrc file.

perdidor avatar May 13 '25 14:05 perdidor

Looks like you misspelled one entry in your torrc config.

HiddenServiceDir /var/lib/tor/jm-dm-service

roshii avatar Oct 02 '25 19:10 roshii