Freenx Not Working With Newly Installed CentOS 6.4

Home » CentOS » Freenx Not Working With Newly Installed CentOS 6.4
CentOS 15 Comments


this is not the same as

I can login with SSH but not with freenx

With 6.3 this worked, I just spinned some new servers and now I can no longer use freenx.

in /var/log/messages:

pr 3 22:05:11 testthuis nxserver[3435]: (nx) Failed login for user

15 thoughts on - Freenx Not Working With Newly Installed CentOS 6.4

  • hi,

    Thanks for taking the time to reply.

    As stated in my message I can log in from ssh. And yes, the password is the same, I have verified it numerous times.

    So no, that is not the problem. And as I wrote in my first message, this has always worked until 6.4. That is why I was asking if anyone else is having this same problem with a new installed 6.4.

    nx is unfortunately very difficult to debug.

    Groeten, natxo

    CentOS mailing list

  • I have bumped the logging to debug level:

    HELLO NXSERVER – Version 3.2.0-74-SVN OS (GPL, using backend: not detected)
    NX> 105 hello NXCLIENT – Version 3.2.0
    NX> 134 Accepted protocol: 3.2.0
    NX> 105 login NX> 101 User: admin NX> 102 Password:
    Info: Auth method: SSH NXSERVER – Version 3.2.0-74-SVN OS (GPL, using backend: not detected)
    Usage: nxserver

    NX> 404 ERROR: wrong password or login NX> 999 Bye

    Is it asking me to change the password?

    Groeten, natxo

    CentOS mailing list

  • I have removed nx and freenx, installed the nomachine packages and everything *just works*.

    I very much would prefer to use freenx, though.

  • Natxo Asenjo wrote:
    Could there have been some crypto as the problem? Where did you install from (remembering US idiot crypto export regs).


  • Freenx defaults to generating a unique client.id_dsa.key – did you install that in the client for each target?

  • hi,

    thanks for taking the time to reply.

    Yes, I copied the client key. I have followed the wiki instructions except


    and adding the users to it with nxserver –adduser

    because we are not interested in that, we use ldap users and that has worked since like for ever, I no longer remember.

  • hi,

    thanks for replying.

    I live in The Netherlands, so I suppose the mirror was automatically chosen in Europe at least. Sorry, I did not pay attention to that. Is there a logfile where I can look that up? in yum.log I can only see that packages get installed/removed.

  • What wiki instructions? I just ‘yum install freenx’ and copy the key to the client. I assumed the real logins (after the key-authenticated nx user) went through pam. Are you seeing anything failing in /var/log/secure?

  • 1st hit on google CentOS freenx:

    in /var/log/secure I just see this:

    Apr 3 23:58:55 testthuis sshd[3803]: Accepted publickey for nx from port 57095 ssh2
    Apr 3 23:58:55 testthuis sshd[3803]: pam_unix(sshd:session): session opened for user nx by (uid=0)
    Apr 3 23:58:59 testthuis sshd[3803]: pam_unix(sshd:session): session closed for user nx

  • hi,

    is it possible for someone to spin a new vm with CentOS 6.4 and the gnome desktop environment, then install freenx and nx and confirm that it works or that it does (or does not) work?

    That would be very helpful.

  • Very welcome…

    So, I just tried GNOME and sure enough it is -not- working for me either…

    I’m using CentOS 64 x86_64, NoMachine as a client and FreeNX on the server. KDE is working…

    I am seeing this in /var/log/messages:

    Apr 5 10:05:47 CentOS-host-0 gnome-session[5181]: WARNING: No required applications specified

    If you google for

    gnome-session “no required applications specified”

    You may see something that is related to the problem. I’m pretty busy today so don’t have time to look into this (and don’t really use GNOME

    This may be of value (from the aforementioned google search):


    Scot P. Floess RHCT (Certificate Number 605010084735240)
    Chief Architect FlossWare

  • Following up a bit late on this, I found out the issue with the failing freenx sessions CentOS 6.4.

    We have a growing freeipa infrastructure (, using the identity management solution delivered by RHEL. ,A colleague installed a host and before joining it to the domain, installed freenx. It worked. So that made me think that the problem was not with freenx but with freeipa.

    Indeed, a joined host to a freeipa domain gets a few options on its ssh client and server config files:

    # diff ssh_config ssh_config.ipa

    # diff sshd_config sshd_config.ipa
    < GSSAPIAuthentication yes 97d95 < UsePAM yes 139a138,143 If we revert the ssh_config and sshd_config files and join the hosts, freenx works again. We lose the known_hosts integration but we already were doing that witch cfengine. For other environments this could be an issue. I will contact the freeipa guys about this issue, but provided freenx is not a part of RHEL, I do not think they will see this as their problem. We’ll see.