Forum Replies Created
-
Posts
-
Hello,
The free version of NoMachine doesn’t support SSH connections. You should check point 1.3 of the installation guide:
https://www.nomachine.com/DT09K00056
This is why ‘nxserver –checkssh reports an error. This is used by other NoMachine products, which support the SSH protocol.
Instead of using ‘nxserver –checkssh’ to verify your installation you can use:
/etc/NX/bin/nxserver –status
The output of the command should be:
NX> 161 Enabled service: nxserver.
NX> 161 Enabled service: nxnode.
NX> 161 Enabled service: nxd.In the case of NoMachine (free), ‘–checkssh’ is unnecessary but harmless. We will remove it.
Hi,
We have reproduced your issue. We have inserted a new Trouble Report at http://www.nomachine.com/TR06L04470. We will fix this problem in the next release.
Hi,
We reproduced the issue related with the main menu in our test laboratory. We also have a workaround for it:
In file:
/usr/share/desktop-directories/NoMachine-dir.directory
Change the line from:
‘Comment=’
to
‘Comment=NoMachine’
This should be enough. If not then log out and log in.
We will fix this issue in the next release.
Value of AvailableSessionTypes entry is reseting during update. This is list of keys which are re-set during every update:
– server.cfgClientConnectionMethods
AvailableSessionTypes– node.cfg
Most of those keys keeps the paths to system tools. The paths are refreshed during every update/upgrade.
CommandFuser
CommandLsof
CommandXdpyInfo
CommandXmodmap
CommandXkbComp
CUPSBinPath
CUPSSbinPath
CUPSBackendPath
EnableCUPSSupport 1 (checks if CUPS is available if YES, set to “1”)
ClientConnectionMethods
AudioInterface (checks which audio tool is available)
CommandStartPulseAudio
EnableSMBFSSupport
AvailableSessionTypesYour old *.cfg file has changed name:
server.cfg -> server.cfg.backup
node.cfg -> node.cfg.backup
You can easly restore your old *cfg file.If any entry during update is duplicated it’s a bug. Could you send more information about the case. A *cfg file with double entries will
be helpful and also /usr/NX/var/log/nxinstall.log and the /usr/NX/var/log/nxupdate.log files from the server side installation.These files you can attach here or send to issues[at]nomachine[dot]com.
Hi,
After the update all services should be working. The update procedure updates the configuration files (*.cfg)
only for adding new configuration keys. Your settings in the *.cfg files shouldn’t be changed, likewise license
files (*.lic) aren’t overwritten and files in NX/etc/keys/ remain the same.No special package. As explained above, the update procedure is intended to preserve current configurations and settings.
If this is not the case, ie. you have found your configuration or keys changed, please tell us what these are.Logs would also be useful which you can attach here or send to issues[at]nomachine[dot]com
We will need the /usr/NX/var/log/nxinstall.log and the /usr/NX/var/log/nxupdate.log files from the server side installation.