Public key authorization failing: Cannot retrieve user home directory

Forum / NoMachine for Linux / Public key authorization failing: Cannot retrieve user home directory

  • This topic has 1 reply, 2 voices, and was last updated 6 years ago by Cato.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #20583
    dstn
    Participant

    Hi,

    This is a duplicate of this reported problem (the solution was not posted on the forum, so it didn’t help me….).

    https://forums.nomachine.com/topic/public-key-authorization-problem

    Short version: when I turn on debug-level logging, in the server logs I see:

    2018-11-22 16:44:18 618.173 82636 NXSERVER _getSupportedKeys nxexec exit code [1], output [], error [NX> 500 Error: Cannot retrieve user home directory.\n]
    2018-11-22 16:44:18 618.308 82636 NXSERVER __getSupportedKeys return:0
    2018-11-22 16:44:18 618.433 82636 NXSERVER Client public key not recognized.
    2018-11-22 16:44:18 618.572 82636 NXSERVER Client request not accepted.
    2018-11-22 16:44:18 618.875 82636 NXSERVER ERROR! Authentication with ‘NX-private-key’ from host ‘10.10.21.100’ failed. Error is ‘Public key not recognized’.
    2018-11-22 16:44:18 619.278 82636 NXSERVER NXMsg: Sending error message ‘NX> 500 ERROR: Cannot accept public key. ‘

    I am logging in using the NX client with username “dlang1”, and if I log in using ssh to the server, I get:

    dlang1@mn001:~$ pwd
    /home/dlang1

    Thanks for any help.

    –dustin

    #20607
    Cato
    Participant

    Hello dstn,

    Is your system configured to use dynamic home directory mounting?
    Can you log on to the desktop of a different user, start terminal, su to root and execute command:

    /bin/bash -c “cd ~<user> 2>/dev/null && pwd”

    where <user> is the name of user which you try to authenticate with key.
    Does it return the proper home directory path?

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.