You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 17, 2023. It is now read-only.
Describe the bug
Connected to remote node on my local network two days ago and opened a channel, using the iOS app, with Zap Technologies. Yesterday and today tried to connect to remote node from outside my local network, but could not connect. Edit4: My node is discoverable and listed on 1ml.com. Another node operator has opened a channel to my node, unprompted by me.
Additional context
Remote node is on a raspberry pi 4 with Samsung SSD. Running bitcoind, not over tor. Fully synced before installing LND. Running LND v0.11.1. Forwarding ports 8333, 9735, and 10009 TCP/UDP to the Pi 4's static IP address. No firewall was added to Raspbian OS. Using lndconnect to generate a QR code which is scanned by Zap iOS. Edit1: I just tried connecting to the remote node using Zap Desktop, and it worked just fine. Edit2: I tried using the same URI that I just used on Zap Desktop, but on Zap iOS, and I connected successfully over home WiFi. Edit3: I thought maybe it was just the QR code, but I just tried using a URI generated by lndconnect (without the -i option) and that did not work. An error is displayed immediately (in less than 0.1 seconds) "Could not connect to server. (Name resolution failure)"
Edit4: My node is discoverable and listed on 1ml.com.
I have tried SO many combinations of options in lnd.conf. I've been searching online for two days to figure out where I went wrong, and nothing has worked. This is the current state of my lnd.conf:
The text was updated successfully, but these errors were encountered:
anon2414691
changed the title
Connected to remote node from within my local network two days ago. Can't connect to remote node from outside my local network, and now I can't connect from inside local network.
Can't connect to remote node from outside my local network, but my node is discoverable and listed on 1ml.com.
Nov 20, 2020
anon2414691
changed the title
Can't connect to remote node from outside my local network, but my node is discoverable and listed on 1ml.com.
Can't connect to remote node from outside my local network, but my node is discoverable and listed on 1ml.com. "Name resolution failure"
Nov 20, 2020
Describe the bug
Connected to remote node on my local network two days ago and opened a channel, using the iOS app, with Zap Technologies. Yesterday and today tried to connect to remote node from outside my local network, but could not connect. Edit4: My node is discoverable and listed on 1ml.com. Another node operator has opened a channel to my node, unprompted by me.
Additional context
Remote node is on a raspberry pi 4 with Samsung SSD. Running bitcoind, not over tor. Fully synced before installing LND. Running LND v0.11.1. Forwarding ports 8333, 9735, and 10009 TCP/UDP to the Pi 4's static IP address. No firewall was added to Raspbian OS. Using lndconnect to generate a QR code which is scanned by Zap iOS. Edit1: I just tried connecting to the remote node using Zap Desktop, and it worked just fine. Edit2: I tried using the same URI that I just used on Zap Desktop, but on Zap iOS, and I connected successfully over home WiFi. Edit3: I thought maybe it was just the QR code, but I just tried using a URI generated by lndconnect (without the -i option) and that did not work. An error is displayed immediately (in less than 0.1 seconds) "Could not connect to server. (Name resolution failure)"
Edit4: My node is discoverable and listed on 1ml.com.
I have tried SO many combinations of options in lnd.conf. I've been searching online for two days to figure out where I went wrong, and nothing has worked. This is the current state of my lnd.conf:
I have tried nat=true, that didn't work.
Expected behavior
Connect to remote node.
Screenshots

Your environment
The text was updated successfully, but these errors were encountered: