Hi,
my umbrel suddenly cannot open any new lightning channels. After filling out the address and the amount of sats, I get:
“Unable to conneect to peer, soks connect tcp xx.xx unknown error general SOCKS server failure”
I read somewhere, that it might be related to the port, but I could previously open channels with addresses with the identical port (9735 in this case).
I also read that it might be connected to TOR, which I of course cannot deactivate and have not fiddled with. Does anyone have a clue, whats going on?
EDIT:
Opening channels isn’t possible from RTL or Zeus on Android either.
Have you tried to restart your Umbrel? Sorry if it’s obvious.
Hi, thanks for the reply! I restarted multiple times and uninstalled RTL, nothing helped so far.
I have the same issue.
Error when opening a channel:
Unable to connect to peer, socks connect tcp [ABCDEFG].onion:9735: unknown error host unreachable.
My node:
- 100% synchronized, up to date, has been running for a few weeks, channels were possible before.
- I tried: shutting down; restarting, reflashing the SD card, restarting after reflashing, waiting if the problem solves itself with time.
After researching the forums, I believe the problem may lie with TOR. I do not know how to solve that except what I already tried (did you try to put the computer off and on again, reflashing…)
The error log which I think is relevant:
Attaching to tor
tor | Jul 10 07:44:20.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor | Jul 10 07:44:21.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor | Jul 10 07:44:21.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor | Jul 10 07:44:21.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor | Jul 10 07:44:21.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor | Jul 10 07:44:21.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor | Jul 10 07:44:21.000 [notice] Bootstrapped 100% (done): Done
tor | Jul 10 07:44:47.000 [warn] Guard brightleopard5 ($3B1790D7B2652D897CECF0D11379EB18F4253C82) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 1/151. Use counts are 0/0. 1 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Jul 10 07:45:03.000 [notice] Guard brightleopard5 ($3B1790D7B2652D897CECF0D11379EB18F4253C82) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 180/258. Use counts are 109/109. 180 circuits completed, 0 were unusable, 0 collapsed, and 6 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Jul 10 07:45:04.000 [warn] Guard brightleopard5 ($3B1790D7B2652D897CECF0D11379EB18F4253C82) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 160/321. Use counts are 111/111. 160 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Jul 10 07:45:04.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 182 buildtimes.
tor | Jul 10 07:45:10.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 239 buildtimes.
tor | Jul 10 07:45:22.000 [notice] New control connection opened from 10.21.21.9.
tor | Jul 10 07:46:25.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $98F793C7320CE3C15A45353AFCC165747A40366D~F3Netze [sSWyZJ/Ab5YjRO5R7Hh0v3/27BvIn4FXHsHgfMP8s0Q] at 185.220.100.255. Retrying on a new circuit.
tor | Jul 10 07:46:40.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $89B13D7F4D42B7952331893BD1484810600FB4A6~flokinet [UgdyUPPeWg/mWlCPs4b36MXdoUGAnjg0lsO4LIxN340] at 185.100.87.202. Retrying on a new circuit.
tor | Jul 10 07:46:55.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $719FD0FA327F3CCBCDA0D4EA74C15EA110338942~F3Netze [Nx05iIqVlLft1v1insRjzT1YbtgXFX+qRtxygcI7GC8] at 185.220.100.252. Retrying on a new circuit.
tor | Jul 10 07:46:58.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 07:47:10.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $6232FDF34FF907DC25A27327D1C05AD370FB2767~niftygreatmother [9JN16aUAu6PsRieE9P3U4g7FaHJC0LiKe/fkucVz9P8] at 185.220.100.246. Retrying on a new circuit.
tor | Jul 10 07:47:25.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $21AE2CE08925E827BB7E7E12A506C7308281527D~ilovemaicatss [k0nl617huEuJEGi7vuw44mVABgE97Hcv8kYI0zLx3rg] at 165.227.178.33. Retrying on a new circuit.
tor | Jul 10 07:47:40.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $14CF04009FFE81448391F3FA626E9D2F114BDE54~hp [qyed3WZVid2Yblrzr2UCJVhgcgZab23IQ97OL16zTrk] at 104.244.74.57. Retrying on a new circuit.
tor | Jul 10 07:47:46.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 07:47:55.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $939126EA4D25CB212A79746C133194F8A24C435B~F3Netze [xrl2f53Rv3b+VoNG/ec2+sXLB2vx2/4sHqxQQw/GvZE] at 185.220.100.253. Retrying on a new circuit.
tor | Jul 10 07:47:55.000 [notice] Tried for 126 seconds to get a connection to [scrubbed]:9735. Giving up.
tor | Jul 10 07:48:01.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 07:48:02.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 07:48:31.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 07:48:42.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Jul 10 07:53:45.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
Else then that:
================
==== Result ====
The debug script did not automatically detect any issues with your Umbrel.
check this one maybe can help.
1 Like
Thanks for replying. The V3_onion_private_key is has a size of 99, so I do not seem to have the same problem. I also replied in the thread linked in your reply.
Then is not this issue. I don’t think is necessary to delete that file then.
1 Like
The issue still remains that I cannot open a channel in Lightning. Someone opened a channel to me (in a channel swap), but I cannot complete the swap on my end 
After the investigation using SSH, I did a final shut down of the umbrel node from within the web interface.
Currently, I can not even access umbrel using the web interface anymore. After accessing the web interface:
This site can’t be reached
umbrel.local’s DNS address could not be found. Diagnosing the problem.
DNS_PROBE_POSSIBLE
Currently reflashing my SD card again…
After reflashing I could access my umbrel. After restarting my umbrel from the web interface, it was behaving normally (e.g. displays the $ equivalent of my sats).
Still stuck with being unable to open channels:
Unable to connect to peer, socks connect tcp [ABZEDFG]:9735: unknown error host unreachable
Here is my umbrel log:
https://pastebin.com/RX09rRsq
I am turning in circles and cannot find the solution.
I was able to open a channel now.
I have no idea what has changed since my last post.
1 Like
Hi, I also have this problem and I have been stuck in opening channels for about a week please help thank you
