Forum Replies Created
Thanks for the feedback.
The NoMachine’s community is amazing ! Keep up on the good work.
Maybe could you explain us:
Whenever server status display “Server is not running”, NoMachine’s services (nxplayer.bin and nxclient.bin) open port and listen incoming connections.
If we want just to use it as a client, why do NoMachine have to listen connection ?
Yes this is a misspeaking, you are right client window is maximized.
Also if you closed both by clicking on close button (NoMachine player then the remote desktop session):
The nx tray icon stay on…..
I found by myself, here how:
You need to modify permissions in ~/.nx/config/authorized.crt
Before nx was able to read this file with owner ( root root ) and permissions set to 0600
Now with this latest update you have to modify the owner with the user profile and permissions set to 0600
The free version is installed on linux debian buster 10.7
Everything was working on 6.11.2_1 with authentification by NX-private-key.
The client is updated also on Windows 10. When I try to connect I get the error message: Authenfication failed
I upgraded it from 6.11.2_1 and now i cannot connect anymore.
Here the error message on nxerror.log file:
“main: WARNING! User ‘xxxx’ unable to read file.”
I would appreciate any help
Here some feedback:
The server was ATOM 2 cores 2 threads.
I had to edit on server side node.cfg to test each modes: (h264, vp8, mjpeg) then i uncommented EnableDisplayServerVideoCodec 0, DisplayServerThreads auto, DisplayEncoderThreads auto.
Lowering the resolution on nomachine help a lot if you stay on h264.
In my configuration, vp8 encoder is lighter and hold up fairly well, you don’t see the processes nxcodec.bin .
I tested on a better processor and no issue at all, so yes h264 encoding need a lot of cpu usage.
And about firefox-esr, it still ask a lot of cpu when scrolling but it s not about nomachine.
Indeed, pressing I and 1 on top command, irxi mode off help to get a better view.
So I consider cpu usage is not so high as i thought on 8 cores. Resolution client side is 5120×3200
server: Intel(R) Atom(TM) CPU C2750 @ 2.40GHz
desktop environnement: xfce without lightdm.
Do you think the cpu’s server cannot handle encoding h264 and could be the reason of high cpu on on a mac client ?
I have the same issue on windows 10 too..
Or maybe this is the good answer:
What is the difference between physical desktop and virtual desktop? https://www.nomachine.com/AR10K00700
Well got the same question, I expect at this answer:
– physical display is when you have a real screen (desktop)
-virtual screen is when you have no real screen (headless server)
maybe someone could bring more details on this feature and which one to choose for desktop or headless server.December 30, 2016 at 10:11 in reply to: Cannot use authentication with SSH/SSL key – free version #13333
I found my answer on server.cfg;
Modify the field:
AcceptedAuthenticationMethods NX-private-keyDecember 30, 2016 at 09:56 in reply to: Cannot use authentication with SSH/SSL key – free version #13332
Here some good news:
– On my ssh server, i created private and public keys, and tested until it works.
– After that, i tried Reza’s recommendation, and it works well ! i can connect by using NX protocol with SSH keys on free version and without using any ssh tunnel.
Maybe I will try with SSL Certificate File and SSL Certificate Key….
But here my last questions
– Can I only allow key authentification on nxserver as on ssh server ? I want to disable password authentication.
– Do you have any jail config and jail filter for NoMachine to use with fail2ban ? I would like to protect my server against attacks.
Thanks for your help.December 28, 2016 at 14:36 in reply to: Cannot use authentication with SSH/SSL key – free version #13309
Thanks for the link, i will try to use ssh keys with your link.
I read this article https://www.nomachine.com/AR10M00866 but doesn’t work either with ssl keys with the free version.
I managed to set a ssh tunnel with putty client (windows port 4003) to linux server (port 4000). And i can connect to NX server with this connection settings:
connection settings: Protocol: NX Host: localhost Port: 4003 Authentication method: Password Username: user Password: ***
The issue is keys authentification (ssh/ssl)