Issues Connecting to Mac

Issues Connecting to Mac

avatar

Been trying to get remote access set up for MacOS (Big Sur) tonight and not having much luck. First I was able to install the agent and get in but found that while I could view, I could not interact with the session at all. The agent was set to allow all activity. Tried later both using the web client and the desktop client. The web client threw the following error
forum image
and the desktop client threw this:
forum image

I was successfully able to add the URL for my bastion server on the MacOS agent config but when I attempted to register it for unattended it would just sit there registering until I had to force reboot the system. I tried running some variations of the PowerShell command in the terminal but nothing worked. Am I doing something wrong?

All Comments (4)

avatar

Hello

There's a few things to unpack here, I'll try to address everything:

> found that while I could view, I could not interact with the session at all

Wayk Agent requires some special permissions in your Mac's privacy settings. You must've enabled screen recording (otherwise you wouldn't see the remote screen); but we also require "Accessibility" in order to inject input (i.e. control) in the remote machine. You can find it in System Preferences > Security and Privacy > Privacy > Accessibility. You need to make sure that "Wayk Agent" is in the list and checked.

(Normally the OS is supposed to prompt you once we try to use accessibility features, but this doesn't always happen. For your information, Wayk has a "privacy dashboard" under Help > Privacy Settings... that can offer insight as well).

> The web client threw the following error

I'll refer this back to the Wayk Bastion team for feedback

> the desktop client threw this

I expect you are hitting a known issue in Wayk 2020.3.x - if you open the Options window, there's a possibility that your login state can be corrupted. On the desktop client, check the login state under Connectivity - if it's "invalid", log out and back in again. This is already fixed internally for the next release; while that was scheduled for this week it's now likely to be pushed back until after the holidays.

> I tried running some variations of the PowerShell command in the terminal but nothing worked

The old "registration UI" should be considered deprecated; it will be replaced imminently with a front-end for the 'wayk-now enroll' command. So you should pursue enrolment using the command line. On macOS, you need to execute against the application executable; so something like this:

/Applications/WaykAgent.app/Contents/MacOS/WaykAgent enroll --token-id {tokenid} --den-url {bastionurl}

If it doesn't work like that, can you post the output from your terminal?

Thanks and kind regards,


Richard Markievicz

avatar

Thank you! I tried the command to register it worked straight away. I checked permissions and it was exactly like you said, I had one that allowed viewing but I missed the one that gave control, all good there. With your advice I was able to connect remotely with a user directly logged into the machine but without a user logged into the Mac, when I attempt to connect unattended, I get this

forum image
or in the web client
forum image

Is that expected?

avatar

Hello

It's not expected but unattended access for macOS is a relatively new addition and is only just becoming feature complete. So we are still smoothing over some parts.

Can you send me /Library/Application Support/Wayk/logs/NowService.log in a PM?

Thanks and kind regards,

Richard Markievicz

avatar

I will get those logs for you, seems def related to a user being logged in at the keyboard. Logged in and got a remote Wayk session open without issue. If I logged out the user while in the Wayk session, this error popped up in web view, the whole browser window went unresponsive and eventually popped this
forum image