-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect Zeus Wallet to myNode using Tailscale set up #727
Comments
Does it have something to do with the lnd setting called "tlsextraip=[YOUR_IP]" It seems as if Tailscale assigns myNode a new IP when activated. Do I need to add that IP to lnd.conf with "tlsextraip=[YOUR_IP]"? |
That may help, but Zeus also has a convenient box to not validate the certificate when connecting. What is the error in LND stopping it from starting? |
I am trying to do this set up so that I can use my lightning wallet when I am on a network other than the one my myNode is on. Does validating the TLS certificate have anything to do with this? In regards to the error, the error on the myNode homepage simply said Network Error, are you looking for a more specific one within the lnd terminal? |
Zeus says if you are using a certificate then to add the hostname to the certificate using tlsextradomain. Could you put an IP in for this value? I'm thinking put in the IP Tailscale gave me. Or maybe do tlsextraip instead. |
Sure, you can add the IP to tlsextraip but you need to regen and the TLS cert afterwards. Zeus has an option to ignore all that though. There's an LND log on the status page. |
I don't think this is a bug. This is probably more appropriate as a support ticket - https://mynodebtc.com/premium_support |
I downloaded Tailscale on my android and on my myNode from the app marketplace. After doing so, I can see both my android phone and the myNode device within the Tailscale app on my phone. However, after enabling Tailscale on my myNode, LND stops working do to a network error. What is the next step in completing this set up?
The text was updated successfully, but these errors were encountered: