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 has been archived by the owner on Nov 17, 2023. It is now read-only.
Describe the bug
I'm being able to connect remotely to my node using Zap when I'm on a regular wi-fi connection (not local). But I'm not being able to connect when trying it on a mobile 4G network.
I'm on a complete different network when trying the wifi approach. And I'm also being able to ssh through the 4G connection but when trying to connect using zap the app refuses to connect.
When trying to scan the lndconnect QR code with my phone already on the mobile network I get the following:
Could not connect to server. (Name resolution failure)
To Reproduce
Try to connect to the node on a 4G mobile network
Connetion fails and app shows nodes list screen.
Expected behavior
Zap should connect to my node when I'm on a mobile 4G network
Describe the bug
I'm being able to connect remotely to my node using Zap when I'm on a regular wi-fi connection (not local). But I'm not being able to connect when trying it on a mobile 4G network.
I'm on a complete different network when trying the wifi approach. And I'm also being able to ssh through the 4G connection but when trying to connect using zap the app refuses to connect.
When trying to scan the lndconnect QR code with my phone already on the mobile network I get the following:
To Reproduce
Expected behavior
Zap should connect to my node when I'm on a mobile 4G network
Your environment
Additional context
I'm currently using a DynamicDNS from http://freedns.afraid.org
The text was updated successfully, but these errors were encountered: