Forum Replies Created
-
Posts
-
The free version of NoMachine has a preloadable virtual session to use in headless environments. This can be controlled by three keys in server.cfg:
Setting CreateDisplay to 1, and then adjusting DisplayOwner and DisplayGeometry to your need.
The startsession command will start Xsession specified in command parameters, or defined by DefaultDesktopCommand config key by default, but only on an already existing Xserver.
Hello,
There should not be any problem with connecting to the EC2 server through NoMachine using username and password combination (using standard configuration).
In your case the issue might be with the username you enter in the Player application – “ec2_IP\ubuntu”. The server’s IP is entered when creating connection, as username it specifies that it is a domain name. When no domain is configured on the server “ubuntu” should be enough.
So please try it like that from NX.If you keep getting “authentication error” using “ubuntu” username though, there could be a problem in your configuration as by default EC2 standard authentication method is by key pair – so in this case please double-check if you do not need to use private key authentication through NX.
Hello.
Thank you for contacting us and reporting your problem.
Unfortunately there is a problem with this Trouble Report and we do not have enough information to proceed. There should be no problem with connecting to xvfb on Amazon EC2 server when configured properly, but as Amazons EC2 servers does not have any session/window managers installed by default there might be a problem with system configuration.
Please, as well as the /usr/NX/var/log directory include the
/home/username/.xsession-errors
file and information about desktop environment configuration to help us evaluate this problem.
Hello.
Thank you for contacting us and reporting this issue.
We have reproduced your problem, and confirmed that when Xcode server is activated NoMachine shows _xcsbuildd desktop instead of the user that is really logged in. We are working on a solution for this problem.
We have also found a workaround that should work for the current NoMachine version:
When server is running and Xcode service is started you can do the user switch to other account which is currently inactive (without logging off), then when you switch back to main account, the NoMachine should now properly recognize it as active.