How to use NoMachine v. 6.8.1 on macOS Catalina

Added on: 2019-10-24 Last Modified: 2019-11-15
ID: AR10Q01057 Applies To: NoMachine Server

Issues reported below are solved by NoMachine v. 6.8.2 for Mac. Updating to v. 6.8.2 or later is strongly recommended. Please consult the following article for details on the correct behaviour: https://www.nomachine.com/AR11Q01061.


Since version 10.14 (macOS Mojave) Apple introduced a new security mechanism which requires special access to be granted in order to control the Mac from remote. In particular for NoMachine, nxnode has to be granted access in the Accessibility Access panel (ref. https://www.nomachine.com/AR10P01001).

The macOS version Catalina 10.15 (19A583) enhanced this security mechanism and requires to set further permissions to let remote desktop applications interact with the desktop and control the mouse and keyboard.

Without such permissions, users can still connect to Catalina desktop via NoMachine but they will see only the background desktop and the upper taskbar. Icons and the Dock are not visible and no interaction with desktop or applications is possible.

With the solution of this Trouble Report, users will be prompted with a system dialog asking to add NoMachine nxnode to Screen Recording, without the need to make the manual operations explained below:
https://www.nomachine.com/TR10Q09433

Cannot interact with a desktop on macOS 10.15 after NoMachine fresh installation

With the solution of this Trouble Report, users will be prompted with a system dialog asking to grant access to NoMachine and nxnode. Accept it to have interactive NoMachine sessions.

A temporary workaround for NoMachine in order to allow interaction with the desktop and until the solution for the above TR is released, is to manually grant access to 'bash'.

During the installation of NoMachine on macOS 10.15, a system dialog is issued for the Accessibility Access (Events). If you're administrator, grant access to 'bash' application by clicking on 'Open System Preferences':

 

 

Allow 'bash' (check it):

 


Finally, it's also necessary to add 'bash' to Screen Recording. There are two ways to do that.

Connect by NoMachine to this Mac: a system dialog is issued to grant access to 'bash' to screen recording functionalities. Click on 'Open System Preferences':

 


and allow 'bash' to record the content of your screen:

 

 

Another way to make the Screen Recording dialog appear is to start the local recording (it's not necessary to save the recorded file): click on the !M icon in the system tray, choose 'Show the recording bar' in the NoMachine menu and press 'Rec'.


Other issues

1) Cannot see any longer my old connections in the NoMachine client UI once upgraded my macOS to Catalina

Workaround
Launch the NoMachine application. The system should issue a dialog asking to grant permissions to NoMachine to access files e.g. on your Desktop or Documents folder. Grant permission to NoMachine from such dialog.

 

 

If the system dialog is not prompted: open Settings ->  Security & Privacy -> Privacy group and select Full Disk Access permission.  Add NoMachine to the list of allowed applications for Full Disk Access.

 

 

2) Cannot see content of a disk connected inside the NoMachine session.

Workaround
Open Settings ->  Security & Privacy -> Privacy group and select Full Disk Access permission.  Add NoMachine to the list of allowed applications for Full Disk Access.
 



3)  Audio is not working in a NoMachine session connected to macOS Catalina.
Ref. https://www.nomachine.com/TR10Q09428

 

Workaround
Change manually permissions of the NoMachine audio driver by executing from a Terminal and restart NoMachine:

sudo chmod -R 755 /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext
sudo chown -R root:wheel /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext
sudo kextutil /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext
sudo /etc/NX/server --restart



4) NoMachine cannot browse the filesystem on Catalina
https://www.nomachine.com/TR10Q09429

No workaround available.


5) When creating a new connection, the private key cannot be added to a new connection file
This problem is related to the Trouble Report mentioned at point 4) but it has a specific workaround.

Workaround
Edit the NXS file to manually add the private key file path to this field:
<option key="Private key" value="" />