-
Notifications
You must be signed in to change notification settings - Fork 46
Could not connect to server (Name resolution failure) #261
Comments
Hey @rex4539 Are you on the same local network? Are you port forwarding and sure your node is accessible? Also, if I recall correctly, the Node Launcher has a |
If it wasn't clear from the bug report, my Zap Desktop connects fine. The mobile one on iOS is failing. |
Hmmm, interesting. What Zap iOS release/version are you using @rex4539? |
Hm, after reading the docs, perhaps I'm having wrong expectations. My expectation was to connect to my local Is there a way to connect to my local node running on my Mac? |
Ahhhh, this explains a lot. It is possible, but not trivial. If you created a wallet within Zap Desktop, then by default you won't be able to. We don't set up the local LND to accept any inbound connections and don't allow outside apps to connect to it for various reasons. However, if you want to, or if you set up LND on your own, you can connect to it given the correct setup. How did you setup LND locally? |
|
My
|
Ok, so this configuration makes the node accessible on your local network. Is your phone on the same network? If you'd like to join our slack, it might be easier to debug this there |
Describe the bug
Zap Mobile cannot connect to server.
To Reproduce
Steps to reproduce the behavior:
lndconnect -j
Expected behavior
Zap mobile connects to server.
What happened
Error message "Could not connect to server (Name resolution failure)"
Your environment
Additional context
Zap Desktop connects to server perfectly.
The text was updated successfully, but these errors were encountered: