bitcoin core – Jointmarket Tumbler / yield_generator concern

I’m unable to get the joinmarket tumbler or yield generator scripts working.

Specifically the script enters a loop, making an attempt to hook up with .onion websites earlier than dropping out and displaying:

[ERROR]  We failed to attach and handshake with ANY directories; onion messaging is just not functioning.

The sendpayment script alternatively works tremendous (regardless of additionally giving the above error).

I’m working joinmarket on an arch machine with tor and bitcoin core each working regionally.

Software program variations:

joinmarket-clientserver-0.9.11
bitcoin-26.0
Tor 0.4.8.12

I believed it may be a difficulty of incoming tor connections however the node accepts connections (out and in) over tor.

bitcoin-cli -netinfo
         ipv4    ipv6   onion   complete   block
in         43       0       6      49
out         3       2       5      10       2
complete      46       2      11      59

I believed it may be a difficulty with SOCKS proxy however netstat suggests appropriate functioning.

netstat -tuln | grep 9050
tcp        0      0 127.0.0.1:9050          0.0.0.0:*               LISTEN

Equally curl –socks5-hostname 127.0.0.1:9050 https://verify.torproject.org suggests connection is efficiently revamped tor.

I’ve tried each with and with out cookie / password authentication. Neither appears to make a distinction.

My Torrc config:

ControlPort 9051
HiddenServiceDir /var/lib/tor/hidden_service/
HiddenServicePort 8333 127.0.0.1:8333

My Joinmarket config:

[MESSAGING:onion]
# onion primarily based message channels should have the precise kind 'onion'
# (whereas the part identify above will be MESSAGING:no matter), and there should
# be solely ONE such message channel configured (be aware the listing servers
# will be a number of, under):
kind = 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 = 8333


[MESSAGING:server1]
channel = joinmarket-pit
port = 6697
usessl = true


# For Tor (beneficial as clearnet different):
host = .onion
socks5 = true
socks5_host = localhost
socks5_port = 9050

## IRC SERVER 2: ILITA IRC (non-compulsory IRC alternate, Tor solely)
################################################################################
[MESSAGING:server2]
channel = joinmarket-pit
port = 6667
usessl = false
socks5 = true
socks5_host = localhost

host = .onion
socks5_port = 9050

My bitcoin config:

server=1
hear=1

## TOR PARAMS
proxy=127.0.0.1:9050
 
# set the management port to entry tor
torcontrol=127.0.0.1:9051
torpassword='' 

Observe, the tor ControlPort 9051 is working efficiently as am ready to hook up with the tor relay utilizing nyx to substantiate in and outbound visitors.

Very puzzled by this concern. Assist very a lot appreciated.