Hey all,
I see in my Umbrel installation a Docker Container named tor_proxy. Looking at the logs I see too many entries like this:
Jan 31 16:46:02.000 [notice] Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
and like this:
Jan 31 16:42:36.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
and like this:
Jan 31 17:01:38.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $A39009A4B0205407B6912D2765A3707E5DCAB167~r0cket12i3 [8mKYcqVRrmQZnjYi5KbXVPldRKsy4OLg/eC7zIncL1U] at 45.84.107.17. Retrying on a new circuit.
and this:
Jan 31 17:30:08.000 [warn] Unable to find any hidden service associated identity key [long-string-here] on rendezvous circuit 3575795663.
Are these notices/warnings bad? Should I be worried and if so, what can I do?
So far I have tried restarting the container several times, but that didn’t help. I also searched online but the findings didn’t seem to match my situation.
I started looking at these logs, because the LND Container had trouble keeping the channels online. I resolved that issue by setting these inside its docker-compose.yml file:
TOR_PROXY_IP: ${APP_BITCOIN_KNOTS_TOR_PROXY_IP}
TOR_PROXY_PORT: ${APP_BITCOIN_KNOTS_TOR_PORT}
or setting the IP address/port of the TOR proxy I use on my local network, instead of the defaults ${TOR_PROXY_IP} and ${TOR_PROXY_PORT}. This has lead me to believe something is going on with the tor_proxy container and looking at its logs.