JP Digital asked 5 months ago
tor connection?
docker exec -it lightning_lnd_1 lncli connect 03da3b1c4891a3c6e37038d629702778775c287f45f229636ccc038ed7f59a0e11@brkyr4n33gvltfwx7hcqam4lmo4dy7wrrltwp3ywry3prwem34ywj6ad.onion:9735
[lncli] rpc error: code = Unknown desc = dial proxy failed: socks connect tcp 10.21.21.11:9050->brkyr4n33gvltfwx7hcqam4lmo4dy7wrrltwp3ywry3prwem34ywj6ad.onion:9735: unknown error host unreachable
[lncli] rpc error: code = Unknown desc = dial proxy failed: socks connect tcp 10.21.21.11:9050->brkyr4n33gvltfwx7hcqam4lmo4dy7wrrltwp3ywry3prwem34ywj6ad.onion:9735: unknown error host unreachable
8 Comments
LN+ Admin wrote 5 months ago
Try peering to the node first? If it's not working we need to reach out to the node operator. They only have one active channel. Maybe there is a technical issue.
JP Digital wrote 5 months ago
Ok I'll reach out to them, thanks.
JP Digital wrote 5 months ago
Is there another way to connect to peers other than cli..is the a way to do it in the GUI
LN+ Admin wrote 5 months ago
What you're showing in your post is the correct way to peer. Can you try to peer (connect) to another node with Tor?
JP Digital wrote 5 months ago
Yea, I actually thought to try that and it worked. I just connected and opened to DarthPikachu, tor node.
LN+ Admin wrote 5 months ago
In this case https://lightningnetwork.plus/nodes/03da3b1c4891a3c6e37038d629702778775c287f45f229636ccc038ed7f59a0e11 has a problem!
BCash_Is_Trash wrote 5 months ago
@LN+: There is a general class of problems related to an incorrect assumption that this site makes: namely, that Tor-only nodes can always connect outbound to clearnet-only nodes. Whether that is possible actually depends on the configuration of the Tor-only node. Many times I have had peers complain that they can't connect to me and get a "Dial Proxy Failed" error when they try. It has always been because their node had been configured to disallow outbound connections to clearnet nodes.
Feature request: Add an option in the LN+ Account Settings for "Can connect to clearnet nodes." Then, if the option is unset, refuse to allow joining Swaps or making Pool requests where an outbound connection to a clearnet node would be needed. (And also refuse to allow clearnet-only nodes to join Swaps or make Pool requests where they would need a Tor-only, no-clearnet node to make an outbound connection to them.)
Feature request: Add an option in the LN+ Account Settings for "Can connect to clearnet nodes." Then, if the option is unset, refuse to allow joining Swaps or making Pool requests where an outbound connection to a clearnet node would be needed. (And also refuse to allow clearnet-only nodes to join Swaps or make Pool requests where they would need a Tor-only, no-clearnet node to make an outbound connection to them.)
LN+ Admin wrote 5 months ago
Thank you BCash_Is_Trash, I will work on this! 👏
Please login to post comments.