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

hhspiny

Member
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

Administrator
Staff member
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

Member
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.
 
Top