Forum / NoMachine for Linux / Can’t change server settings
- This topic has 15 replies, 3 voices, and was last updated 4 years, 5 months ago by cfilipescu.
-
AuthorPosts
-
May 14, 2020 at 17:16 #27481cfilipescuParticipant
I can’t change the server settings from the GUI because I keep getting a prompt to “Please insert a user with administrative rights”.
I tried adding the user as an administrator, nxserver –useradd <username> –administrator
I tried uninstalling and reinstalling, which also didn’t help.
This problem only occurred after many months of having NoMachine installed, and after a fresh fedora install, I don’t have the same problem. However wiping my hard drive clean is not a solution.
I am running Fedora 31, but NoMachine was originally install on Fedora 30 and over time I updated the distro.
Has anyone encountered this problem before?
May 15, 2020 at 14:04 #27521ewiredParticipantThis is happening for me after the latest update yesterday. I’m no longer able to use NoMachine at all on any of my two systems. I wish I could downgrade to the previous version. When running nxclient –admin as root, I see a server running, but it does not allow any user to connect (authentication error). When running nxclient –admin from the menu icon as usual, it does not allow me to change settings, as it now prompts to “Please insert a user with administrative rights” and does not allow any user, even though my user has sudo.
While NoMachine is out of service, I’m using vino-server which is built into GNOME, and accessing my screen over VNC. I had to start it in the command line because my distro is special, but on Fedora you should be able to go to GNOME settings, then Sharing, enable sharing, then enable screen sharing. This will start a VNC server that you can use from Remmina or KRDC.
May 26, 2020 at 14:58 #27780graywolfParticipantHello.
What do you get running
sudo -l
with your user? You should get something likeUser xxxxxx may run the following commands on yyyyyy:
(ALL) ALLIs there any error logged in /usr/NX/var/log/nxerror.log or in $HOME/.nx/*/session ?
May 27, 2020 at 09:10 #27790graywolfParticipantPlease compare if they differ:
- Running
sudo -l
using a shell owned by your user - Running `sudo -l -U “myusername”
Report the output of commands:
- authselect current
- grep sudoers /etc/nsswitch.conf
May 27, 2020 at 10:38 #27782cfilipescuParticipantHi,
When running sudo -l the following is present:
User may run the following commands on :
(ALL) ALLOutput of cat /opt/NX/var/log/nxerror.log:
98785 98862 10:21:46 737.057 DaemonParser/Parser: WARNING! Creating directory '/var/NX/nx/.nx'.
awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator
98785 98871 10:21:50 747.871 ServerNetworkInfoHandler: WARNING! Obtaining network data failed.Output of cat $HOME/.nx/*/session:
Info: Slave server running with pid 100487.
Info: Listening to slave connections on port 25001.
Info: Starting NoMachine Monitor version '6.10.12'.
Info: Loaded translation files for 'English'.
100474 100474 10:25:16 275.156 OsDetect: Setting os type to 'Fedora'.
100474 100474 10:25:16 275.178 Main: Creating a new connection monitor.
100474 100474 10:25:16 489.728 ClientThread: Creating new thread.
100474 100474 10:25:16 945.943 MonitorService: Enabled drag and drop feature.May 27, 2020 at 10:39 #27786ewiredParticipantI am getting (ALL) ALL for sudo -l on the remote machine.
Tailing $HOME/.nx/*/session, no new errors are produced when connecting to the remote.
Tailing /usr/NX/var/log/nxerror.log, some errors are produced when connecting to the remote:
Info: Handler started with pid 132450 on Tue May 26 19:41:58 2020.
Info: Handling connection from 10.42.0.1 port 48780 on Tue May 26 19:41:58 2020.
132497 132497 19:44:48 001 nxexecPAMCheckCredentials: ERROR!Authentication failed with error 7.
Info: Connection from 10.42.0.1 port 48780 closed on Tue May 26 19:44:48 2020.
Info: Handler with pid 132450 terminated on Tue May 26 19:44:48 2020.10.42.0.1 is local, 10.42.0.151 is remote.
I also noticed some logs before I attempted connecting when reading the tail of the log file, but these are not reproduced on reconnect:
130078 130078 18:50:00 947 nxexecExecute: ERROR! Cannot execute '/usr/NX/scripts/restricted/nxenvironmentget.sh': Permission denied.
130083 130083 18:50:00 955 nxexecExecute: WARNING! Can't set suplementary groups.
130083 130083 18:50:00 955 nxexecExecute: WARNING! Error is 1.
130083 130083 18:50:00 955 nxexecExecute: ERROR! Cannot execute '/usr/NX/scripts/restricted/nxenvironmentget.sh': Permission denied.
130088 130088 18:50:00 963 nxexecExecute: WARNING! Can't set suplementary groups.
130088 130088 18:50:00 963 nxexecExecute: WARNING! Error is 1.
130088 130088 18:50:00 963 nxexecExecute: ERROR! Cannot execute '/usr/NX/scripts/restricted/nxcookieget.sh': Permission denied.
130093 130093 18:50:00 971 nxexecExecute: WARNING! Can't set suplementary groups.
130093 130093 18:50:00 971 nxexecExecute: WARNING! Error is 1.
130093 130093 18:50:00 971 nxexecExecute: ERROR! Cannot execute '/usr/NX/scripts/restricted/nxenvironmentget.sh': Permission denied.I tried to set permissions of /usr/NX/scripts/restricted to 771 but this didn’t fix the issue, connections still fail with the PAMCheckCredentials error.
May 27, 2020 at 10:40 #27787ewiredParticipantI applied the fix found in this thread:
https://forums.nomachine.com/topic/authentication-failed-with-error-7
chmod u+s /usr/NX/bin/nxexec
This allows me to manage server settings without being prompted for a user, and to connect to the server again. However, it does not detect any displays and prompts to create a new one which is not my physical display. The NoMachine tray icon still does not show up even after a reboot, although nxclient –admin does report that the server is running.
May 27, 2020 at 10:40 #27788ewiredParticipantI uninstalled NoMachine by following this:
https://askubuntu.com/questions/583547/how-to-uninstall-nomachine
Then, I reinstalled NoMachine according to the guide for my distribution. So far, this issue is solved for me and I’m able to connect to my physical display. I was hoping I wouldn’t have to reinstall, but thankfully the process to uninstall and reinstall NoMachine is very quick and I should have tried it sooner. Thanks!
May 27, 2020 at 11:30 #27805graywolfParticipantHi,
When running sudo -l the following is present:
User may run the following commands on :
(ALL) ALLHello, what about these:
authselect current
grep sudoers /etc/nsswitch.conf
sudo -l -U myusername
(in a root shell)
May 28, 2020 at 07:26 #27815cfilipescuParticipantHi,
Output of authselect current:
Profile ID: sssd
Enabled features:
– with-fingerprint
– with-silent-lastlogThere is no output when running grep sudoers /etc/nsswitch.conf.
When running sudo -l -U myusername (in a root shell) the following is present:
User may run the following commands on :
(ALL) ALLMay 28, 2020 at 11:21 #27826graywolfParticipantMay I send a debugging version of a server component? Would you try it?
May 28, 2020 at 17:33 #27828cfilipescuParticipantYou can send me a debugging version, I’ll try it.
June 5, 2020 at 11:10 #27994graywolfParticipantcfilipescu: it looks your sudo command returns CRLF as line terminator. That would be a problem, by the way future versions will address it. It is unusual that commands on Unix systems do that, I’m curious: how is it set up?
June 18, 2020 at 07:55 #28170cfilipescuParticipantI don’t have a special setup, I use Fedora 32 with fish shell instead of bash. I am not sure why sudo returns CRLF as line terminator.
June 25, 2020 at 15:02 #28296graywolfParticipantHello, would you try latest version (6.11.2)?
- Running
-
AuthorPosts
This topic was marked as solved, you can't post.