Lightning Channels - Unable to connect to peer

Bitcoin and Lightning
1

Error message in LITD:

UNABLE TO CONNECT TO PEER
rpc error code = Unknown desc = dial proxy failed: socks connect tcp
ip address:9050-
>ip address:26658: unknown error
TTL expired

2

It looks like you’re encountering a networking issue, possibly related to a proxy connection or a socket error. Here are a few steps you can try to troubleshoot the problem:

  1. Check Proxy Settings: Ensure that your proxy settings are correctly configured. If you’re using a SOCKS proxy, verify that the IP address and port (9050 in this case) are accurate.
  2. Network Connectivity: Test your internet connection to ensure it’s stable. You can do this by trying to access a website or running a ping test.
  3. Firewall/Antivirus: Check if your firewall or antivirus software is blocking the connection. You might need to add an exception for the application you’re using.
  4. TTL Settings: The “TTL expired” message indicates that packets may be getting lost or that there’s a routing issue. You could try resetting your router or checking your network configuration.
  5. Retry the Connection: Sometimes, simply retrying the connection can resolve transient issues.
  6. Logs and Documentation: Look at the logs for more detailed error messages. Documentation for the application you’re using might also provide specific troubleshooting steps.

If you still face issues after trying these steps, providing more context about the application and your setup might help in diagnosing the problem further.

3

Thanks for the help!

  1. Check Proxy settings:

I believe they are correct as 10.21.21.11:9050 as this is apparently the “IP within the Container”.

  1. Good network connection. However, from terminal in the umbrel node,
    ping -c 3 8.8.8.8
    ping: socktype: SOCK_RAW
    ping: socket: Operation not permitted
    ping: => missing cap_net_raw+p capability or setuid?

  2. Opened ports 8333, 9050, 9001 to the device on my router.

  3. Hmmm…maybe

  4. Tried many times

  5. Yes, working on that.

4

Will mark this as closed. I think I didn’t have the ports opened on the router correctly.

1 Like
5
  • You don’t need port forwarding on your router for Tor
  • It’s more likely a temporary connection failure of the Tor onion network

This happens quite often, and obfuscate by design, but likely that the Tor part your peer uses has a connection problem with the Tor part your node uses. Restarting Tor creates a new entry gateway and rebuilds your Tor hops into and out of the network, which may resolve it for you. But keep in mind, that if you intend to run a high available / routing / speedy node, you can’t rely on Tor alone unfortunately.