Thanks for maintaining this, especially the fun task of mapping the paths nomachine uses.. As mentioned, please don't change this as I think it'll randomly break something (either today or in a future release) that would be a PITA to track down.
I've been using nomachine to access my machine remotely (duh?) as I've been away a bit and needed UI for a few things. The free version works great for this simple usecase.
This is great when using Wireguard, makes it super simple.
The config outlined on the wiki work really well for headless (as of June 2023, will keep working as it's pretty stable IMHO), around tweaking the pam.d config for headless.
Pinned Comments
runnytu commented on 2021-02-20 13:44 (UTC)
Since nomachine 7.1.3-2 the default behavior of the package is StartNXDaemon Manual and FirewallConfiguration 0 on a new installation, if you want to change this, you need to modify PKGBUILD build options with your desire behavior:
BUILD OPTIONS
Set to y to enable nomachine service autostart
_autoservice=n
Set to y to enable firewall autorules
_autofirewall=n
END BUILD OPTIONS