Hi all, in the Android Mysterium app and Deskopt app, it happens when a client loses connection to the node [when the node goes offline randomly like an internet connection outage or downtime of the mysterium node]. The customer gets stuck in "On Hold" status and until reconnecting, their Internet connection is blocked, unable to access the Internet. Because the Mysterium client app is acting like it's still connected even though it's not, and therefore blocking the whole internet traffic of the client device, until the client notices it and does re-connect to some working node.
Many people are reporting this problem on the Google Play Store, and developers still tend to ignore this critical bug in the app. It is stated somewhere in the Mysterium documentation that when a client loses connection to a node, it is automatically reconnected to a working one. But it doesn't. It just gets stuck in "On Hold" status and blocks the whole client's internet access.
Hi all, in the Android Mysterium app and Deskopt app, it happens when a client loses connection to the node [when the node goes offline randomly like an internet connection outage or downtime of the mysterium node]. The customer gets stuck in "On Hold" status and until reconnecting, their Internet connection is blocked, unable to access the Internet. Because the Mysterium client app is acting like it's still connected even though it's not, and therefore blocking the whole internet traffic of the client device, until the client notices it and does re-connect to some working node. Many people are reporting this problem on the Google Play Store, and developers still tend to ignore this critical bug in the app. It is stated somewhere in the Mysterium documentation that when a client loses connection to a node, it is automatically reconnected to a working one. But it doesn't. It just gets stuck in "On Hold" status and blocks the whole client's internet access.