Authentication Failed: ERROR! kDestroy does not exist

Forum / NoMachine Cloud Server Products / Authentication Failed: ERROR! kDestroy does not exist

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #13933

    I am using NoMachine Small Business Server 5.2.11 on my Ubuntu. After updating to current (latest) version, I can’t edit any settings for my NoMachine server, because I get “Authentication Failed error, please try again”. Before the update, I was able to make changes with my user. Restarting machine, reinstallation doesn’t help. Any suggestion how to resolve this issue?

    Or if you now how to set Auto-Lock screen on a server when connecting in a different than UI way, that would be enough for me.


    My dump from nxerror.log

    17818 17818 10:43:45 676.339 NodeRemoveKerberosTicket: ERROR! kDestroy does not exist.

    17818 17818 10:43:45 684.765 Io/Io: WARNING! Can’t find pid monitor for 3570.

    17761 17761 10:43:46 356.949 HostWmRunning: WARNING! Giving up after 500 Ms.

    17761 51365 10:43:51 723.100 HostWmRunningHelper: WARNING! Failed to open display ‘:0’.

    nxexecRestoreSavedResourceLimits: Info: Can not open resource limits file.

    nxexecRestoreSavedResourceLimits: No such file or directory.

    nxexecExecNode: Info: Cant not restore saved resource limits.

    nxexecGetUserInfo: Got error 0.

    nxexecGetUserInfo: The given user name was not found: <myusername>.

    Error: Authorization failed.


    Hello milosg,

    We need logs from your NoMachine server machine. Please, use these instructions:, and send them to forum[at]nomachine[dot]com.

    Excerpts which were provided by you suggest that NoMachine fails to start nxnode process, because it can’t validate user. If you use some specific technology for user management, like LDAP or Active Directory, it’s possible that you need to adjust ‘/etc/nsswitch.conf’ file to include alternative sources of user information.

Viewing 2 posts - 1 through 2 (of 2 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.