I followed the procedure and my LND can't connect to any LN node

[houten11]

I've successfully connected my local node to openvpn server. Everything seems fine in openvpn logs, but when I start lnd, lnd logs are full of timeout or network unreachable lines:

[ERR] SRVR: Unable to connect to 037bac010f84ef785ddc3ade66d008d76d90d80eab6e148c00ea4ba102c07f2e53@3.238.22.25:9735: dial tcp 3.238.22.25:9735: i/o timeout
[ERR] SRVR: Unable to connect to 03573d821ac340980ea15ae2e84bfd0365690b459f0192c946fe49fb5bdda8736a@[2003:ce:7f18:7c00:c2f3:2dcf:1e3a:f7c]:9735: dial tcp [2003:ce:7f18:7c00:c2f3:2dcf:1e3a:f7c]:9735: connect: network is unreachable

Os: Ubuntu 22.04 Lnd is: lnd v0.15.1-beta

@TrezorHannes do you have some suggestion what might be the issue, or how can I debug the problem? lnd, docker and vpn client logs doesn't show anything usefull.

[TrezorHannes]

Hey - thanks for logging your issue here.

Let's get some more details. The two logfile entries first 1) [ERR] SRVR: Unable to connect to 037bac010f84ef785ddc3ade66d008d76d90d80eab6e148c00ea4ba102c07f2e53@3.238.22.25:9735: dial tcp 3.238.22.25:9735: i/o timeout assuming this is a channel-partner of you 4dfc48297fc8, he/she has not setup their node properly. The connection defined to connect to their node is reporting the 9735 port closed. Follow this link and enter their IP and port, you can verify this by yourself. When their port isn't open, your node doesn't get a successful response.

2) [ERR] SRVR: Unable to connect to 03573d821ac340980ea15ae2e84bfd0365690b459f0192c946fe49fb5bdda8736a@[2003:ce:7f18:7c00:c2f3:2dcf:1e3a:f7c]:9735: dial tcp [2003:ce:7f18:7c00:c2f3:2dcf:1e3a:f7c]:9735: connect: network is unreachable This is an IPv6 connection. Note that the guide doesn't incorporate tunneling your IPv6 LN packages. So you'd need to either enter those functionalities yourself, by adding ip6tables forwarding to the VPS OpenVPN docker, or removing the IPv6 listen entry in your own lnd.conf. I'd recommend the latter, since IPv6 is rarely used by LN-Nodes.

Lastly, let's check if your node Hybrid is working

• Add your VPS IP and LN port into https://portchecker.co/check and see if the port is open
• Provide your Node's Pubkey here, I'll try to see if I can successfully connect via Clearnet

Hope this helps - congrats on making this approach!

[houten11]

Some of the timeout errors are for healty nodes:

[ERR] SRVR: Unable to connect to 029c20772e97f6ce82d2dd15f589182d4fd1d15c582819fe017da7d8215f534dc1@144.91.102.16:9735: dial tcp 144.91.102.16:9735: i/o timeout

I also tried to connect to bitrefill node manually and got timeout again:

[DBG] SRVR: Connecting to 030c3f19d742ca294a55c00376b3b355c3c90d61c6b6b39554dbc7ac19b141c14f@52.50.244.44:9735
[ERR] SRVR: Unable to connect to 030c3f19d742ca294a55c00376b3b355c3c90d61c6b6b39554dbc7ac19b141c14f@52.50.244.44:9735: dial tcp 52.50.244.44:9735: i/o timeout
[ERR] RPCS: [connectpeer]: error connecting to peer: dial tcp 52.50.244.44:9735: i/o timeout
[ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: dial tcp 52.50.244.44:9735: i/o timeout

Lnd port is opened.

I intend to run only over clearnet(VPS+Tunneling), no Hybrid mode.

Also is there are a reason bitcoind has to be run over tor, can't we tunnel bitcoin traffic through VPS as well?

[TrezorHannes]

Let's look at the stuff together.

1. Can you provide the result of lncli getinfo, or lncli getinfo | jq .uris: do you have the clearnet uri listed?
2. Verify that you added the 3 iptable rules inside the docker container on the VPS, as described here.
3. Does curl ifconfig.me report back your VPS external IP?

On your bitcoin Tor question

• Tor is actually going through the tunnel, like all of your packets now. You'll see with point 3) above, or traceroute, that every paket from your node is now tunneled via VPS.
• there is no technical need for bitcoin going clearnet, since time / speed is not of essence. So you can keep bitcoin via Tor, even though it's a bit of a double-anonymization (Tor within Tunnel)

[houten11]

Finally got it working. The problem was VPS docker instance didn't have internet access. I'm not really sure why. It could be some docker or host machine setting. I was using this VPS instance for a long time, so maybe I miss configured something in the past. Anyway when I tried with a new VPS instance, everything worked smoothly. Thanks @TrezorHannes for your help.

[TrezorHannes]

Great, glad you got it!