Package Details: nomachine 8.16.1-1

Git Clone URL: https://aur.archlinux.org/nomachine.git (read-only, click to copy)
Package Base: nomachine
Description: Remote desktop application
Upstream URL: http://www.nomachine.com
Licenses: custom:"NoMachine EULA"
Groups: network
Conflicts: nxclient, nxmanager, nxnode, nxserver, nxwebplayer
Submitter: FreeK
Maintainer: runnytu
Last Packager: runnytu
Votes: 95
Popularity: 0.44
First Submitted: 2014-07-24 15:45 (UTC)
Last Updated: 2025-02-01 20:34 (UTC)

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

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 25 Next › Last »

kirk commented on 2020-07-01 15:02 (UTC)

Is it possible to install only nxserver and necessary daemons on my remote machine I want to access into? I don't need the client there since I'm gonna use from the client to access the remote machine.

galvez_65 commented on 2020-06-22 02:12 (UTC) (edited on 2020-06-22 02:12 (UTC) by galvez_65)

@LoopBack It's documented in the PKGBUILD file, you need to edit it to turn that off.

LoopBack commented on 2020-06-22 01:08 (UTC)

Recently with every update , the service is started and enabled at startup. I keep having to stop it and disable autostart with PC.

How do I stop this insecure behavior?

Thank you!

hcjl commented on 2020-06-20 13:21 (UTC)

@Le_Birlante, thanks for addressing this to NoMachine. I am also waiting for the fix.

RLLBcheese commented on 2020-06-17 11:26 (UTC)

$pkgver needs to be updated to 6.11.2. 6.10.12 is producing a webpage AFAICT.

You can work around the out-of-date package by downloading http://download.nomachine.com/download/6.11/Linux/nomachine_6.11.2_1_x86_64.tar.gz (or as appropriate for your $arch), running sha512sum on that file, updating the $pkgver and appropriate sha512sum_$arch line in the pkgbuild, then running makepkg -si.

greyltc commented on 2020-06-16 19:28 (UTC)

checksums failing for anyone else?

lucasrizzini commented on 2020-05-27 08:00 (UTC)

I don't know if this is a joke or not. Just go search through settings, man.

bradsk88 commented on 2020-05-26 21:37 (UTC)

Does anyone know how to configure this to use a different port than the default 4000?

galvez_65 commented on 2020-05-16 15:50 (UTC)

Anyone having issues connecting to a server running GDM? with GDM 3.36 if I try to remote into a machine which I am not already logged into I get a white screen. If I am physically logged in I can remote in without issue. Rolling GDM back to 3.34 resolved the issue for me.

pmatos commented on 2020-05-12 18:39 (UTC)

I am getting:

==> Validating source_x86_64 files with sha512sums... nomachine_6.9.2_1_x86_64.tar.gz ... FAILED