Suggestion -- option to past denied access device to authorized device

[hhspiny]

Right now, the authorized device is added only via the dialog box that pops up. this creates two problems
1. the dialog box disappears after a while
2. run in booter mode (i.e. no remotly instance in user account), the dialog box does not pop up at all.

Suggestions, list the devices that have attempted to access but were denied, then allow manually add to authorized device list.

 

[mirillis]

Hi hhspiny,

"1. the dialog box disappears after a while"

When the box disappears, another one should pop up with a 60 seconds countdown where another authorized user can connect remotely and add the previous device which attempted to connect to authorized list.
Personally I have my mobile device authorized on all devices and use this device to authorize other devices remotely.

"2. run in booter mode (i.e. no remotly instance in user account), the dialog box does not pop up at all."

This worked in the past in lock screen (but no in desktop of another user). For example when no user was logged in and only booter was running., you could connect to it and there was a popup with authorization request. It there was no one to authorize the connecting device by the host a similar situation to this in point (1) above was possible. Another authorized user could authorize the device after connecting.

BUT after recent Windows updates showing popups in lock screen seems not to work anymore. I will double check it before final 1.34.0 update.

"Suggestions, list the devices that have attempted to access but were denied, then allow manually add to authorized device list."
We could use the "recent inbound connection list" to make this. For example this list would not only show the connecting login but also the device and add a button to authorize it "offline".

BTW. The login problem when network connection is not stable should finally be fixed in 1.34.0. Unfortunately this requires another master server update though (should be done next week after 1.34.0 release). So it's best to have 1.34.0 installed to make sure all devices will re-login after master server update.

BTW2. One more thing will be added to 1.34.0 - remote gamepad vibration.

 

[hhspiny]

I would vote for extending the inbound connection list to allow adding to authorized list. mobile phone works, but you need to be around. what if you need to authorize for someone else, and you don't want to do it right then, but rather to take care of it later, and in batch.

 

[mirillis]

I can confirm that Windows is now blocking any system popup windows in the lock screen (like our authorization message box). I'm not sure when this happened but it does not work on Windows 10 and 11 (still works on 8.1 and 7).

We will add batch authorization of devices to inbound connection history in 1.34.1.

We are almost ready with 1.34.0. We are having some serious trouble with latest Nvidia drivers (580.xx). There are still problems running these drivers but it's not our fault. Probably they have started using more AI for testing :/

 

[hhspiny]

It would be even better if a specific device(s) within an account is designated as the authorizing device, and shows a notification. or the authorization function can be centralized on the web portal.

i.e. batch authorization for multiple hosts. if you have a group of hosts, and want to add an authorized client to all of them. image the effort it entails.

 

[mirillis]

For now there will be a "mark all for authorization" in the inbound connection log. So it will be possible to authorize devices one by one, or all at once.

Another thing is that it seems hardware acceleration does not work stable for booter in lock screen. But it works ok in desktop of any user that has logged in. We will remove hardware acceleration for login/lock screen for booter.

 

[hhspiny]

a potential bug in 1.34 -- if an unauthorized client is connected and waiting for authorization, no other client can make connection.

 

[mirillis]

The authorization popup should time out after 60 seconds and connection can be done again.

 

[mirillis]

BTW. There was a bug that prevented Multi-Join connection when an unauthorized device locked remote host by showing authorization popup.
This has also been fixed and now another user can connect even when the popup is visible.