Hi Everyone,
A lot of Remotly users have asked us why does a local network connection (hosts and clients connected in the same LAN) disconnect when the local network loses internet access, even when the host and client are still visible to each other.
We want to explain why this happens and inform you about upcoming improvements in this area.
Each remote host state (online, offline, information about whether it is locked etc.) can be accessed from any remote place, not just the local network.
That's why each host has to notify state servers about it's current state to keep everything synchronized.
A real life situation:
1. You are connecting to your host which is in the same network as your Android/iOS client
2. Connection is established and everything works like a charm
3. Suddenly your network loses internet access
4. Some other device is logged using your account from a different network or you have invited someone to your host device
5. This person will see this host as offline as it is no longer reachable from outside of your network
6. Your connection is disconnected in the local network which can be annoying as it could still work
What we want to do is to keep the connection alive even when internet access is dropped.
Anyone from outside your local network will see your host device as offline (until internet connection is restored in the network where the host is located).
In one of the upcoming updates this will no longer happen.
A connection will be sustained as long as it can until a manual disconnect is done.
A lot of Remotly users have asked us why does a local network connection (hosts and clients connected in the same LAN) disconnect when the local network loses internet access, even when the host and client are still visible to each other.
We want to explain why this happens and inform you about upcoming improvements in this area.
Each remote host state (online, offline, information about whether it is locked etc.) can be accessed from any remote place, not just the local network.
That's why each host has to notify state servers about it's current state to keep everything synchronized.
A real life situation:
1. You are connecting to your host which is in the same network as your Android/iOS client
2. Connection is established and everything works like a charm
3. Suddenly your network loses internet access
4. Some other device is logged using your account from a different network or you have invited someone to your host device
5. This person will see this host as offline as it is no longer reachable from outside of your network
6. Your connection is disconnected in the local network which can be annoying as it could still work
What we want to do is to keep the connection alive even when internet access is dropped.
Anyone from outside your local network will see your host device as offline (until internet connection is restored in the network where the host is located).
In one of the upcoming updates this will no longer happen.
A connection will be sustained as long as it can until a manual disconnect is done.