Hi Ry,
Please try this pre-release 1.17.0 version:
https://downloads.mirillis.com/files/beta/remotly_pc_1_17_0_setup.exe
Please note that this new version will change the current connection ID to the new 14 letter/digit format. The old one will be replaced.
Do you have access to an Android mobile device? If so can you try to login via Remotly mobile app (you should be able to find it by searching "Remotly" in Google Play or you can use the link in the download section).
Please send me the email address associated with your Remotly account in a...
Hi Ry and welcome to the forum.
You should not experience this problem after the latest mother server fix. Users Fu2chN and gaetanolip reported that the login now works for them on the PC server.
Can you log in to your account using the web browser? Can you access your admin panel online?
We...
Actually the error was not in the app but on the mother server side. We have added an additional fix also for the app in case the "zombie" device would happen again. It will be included in v1.17.0 that will be released tomorrow.
We have just uploaded the newest version of the Android app to Google Play Store (still awaits approval) and the APK is also available in the download section.
What's new:
- Added support for new 14 digit/letter Connection ID codes that will be introduced in PC version 1.17.0
- Added Acoustic...
Hi bananaman,
You don't have to accept the device manually every time you connect. You can add the client device used for connection to the trusted list and it will let this device in without authorization (when connecting with ID or using device name).
The authorization fingerprint is created...
The problem was very complicated and hard to repeat. During a master server update (or possibly in some other situation) the automatic re-login process was not completed fully (only partially) because of some network timeout or something similar. This left a device in a "zombie" like state (but...
The problem should now be fixed. The login problem was reported for a long time and was difficult to trace but from now on it should not happen anymore.
Unfortunately the problem is more serious and there might be a problem with login to user's account on such device. So if you see "online" state for a device and will try to login to it on PC (it works from admin panel and mobile app as these are only clients) it might give you "Login failed"...
We have found the problem. We are working on it. I will let you know when it's fixed. It might just start working or and update of the server to v1.17.0 will be needed.
Yesterday, the mother server was updated and restarted. We have been informed that some hosts have not logged in properly and are unreachable (the host state is "online" but clients cannot connect to them showing error -1). We are investigating this problem and hope to have a fix for v1.17.0...
We are targeting end of autumn. We also have a hardware device in our plans that will allow to play any console game (ps4/5, xbox and nintendo) on any low power device with up to 4 players.