Forum Replies Created
Please can you try to change key AudioInterface in node.cfg
and then restart NoMachine server using
sudo /etc/NX/nxserver --restartSeptember 8, 2023 at 15:10 in reply to: SSH is working fine, but not able to connect via NoMachine. #45347
If you are using NoMachine free version, you will not be able to use SSH protocol. When you try to connect with SSH you will receive message in player
Running NoMachine sessions over a SSH connection is not supported on this server. Do you want to switch your connection to using the NX protocol?
If you would like to use SSH, please use some of NoMachine enterprise products.
There was upload error, can you send log file to to the forum[at]nomachine[dot]com?
We still did not have full logs, as I have missed to ask after enabling debug logs to restart server and then to reproduce problem. Please can you redo it and then provide us with logs.
sudo /etc/NX/nxserver --debug --enable all sudo /etc/NX/nxserver --restart
It seems that what you mentioned “The Centos7 workstation is not connected to a monitor” could play a role in the problem that NoMachine does not detect it as available session, and when NoMachine tries to create new display, that request fails as there is already display number used.
Logs from the server side would be useful. Enable debug on the CentOS 7 machine, reproduce the problem and then gather up the logs.You can send them to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email.
sudo /etc/NX/nxserver –debug –enable all sudo /etc/NX/nxserver –debug –collect sudo /etc/NX/nxserver –debug –disable all
I could propose workaround to try so NoMachine will create new display with a new display number.
/usr/NX/etc/node.cfgby enabling key
PhysicalDisplays :3.June 6, 2023 at 12:32 in reply to: Session type unix-xsession-default is not available on node #44496
I tried to understand the problem and only case that I could think about is that key unix-xsession-default is removed, or not present in the server.cfg or node.cfg on the node where you want to run session.
You can verify it by checking configuration files on the node by following command:
grep ^AvailableSessionTypes /usr/NX/etc/node.cfg /usr/NX/etc/server.cfg
If key unix-xsession-default is not present, add it in the AvailableSessionTypes and then execute:
sudo /etc/NX/nxserver --configupdate
As well you could execute on ETS
sudo /etc/NX/nxserver --resourcelist --class session --node nnn.nnn.nnn.nnn:4000to check if the session type is enabled.
If that does not help, can you share your server.cfg and node.cfg files from ETS and ETSN.You can attach them here or send to forum[at]nomachine[dot]com, by referencing this topic.
I have tried now on Samsung Galaxy S10+ with Samsung Dex and worked perfectly even when using wireless Dex option.
Additionally about mouse events, they all worked correctly left, right click and as well mouse middle button.
Possibly you can tell us what is the physical mouse you used, and what Linux OS.
I tried to reproduce on different machines but without success this problem. It looks that there are some issues with access to the fonts. I would recommend that possibly you try to clear and rebuild macOS font database.
sudo atsutil databases -remove sudo atsutil databases -removeUser sudo reboot
If that does not help, please check if the same problem is present when using another user, and it would be good to verify if in system logs there are information about font problems.December 22, 2022 at 17:04 in reply to: Ubuntu host no display unless dummy dongle plugged in after client connection #42106
Ut is up to a system, GPU configuration how it handles headless screen.
To setup NoMachine to work headless you can follow this article. https://kb.nomachine.com/AR04R01083December 22, 2022 at 16:53 in reply to: Grey screen at GDM login page on-Fedora 36 with Wayland #42104
Enabling egl capturing in NoMachine does require modification of the desktop startup scripts.
You can see more information in the following article https://kb.nomachine.com/AR04R01083.
sudo /etc/NX/nxserver --egl-capture yesdoes not disable wayland and does not force x11.
If I correctly understood your question is that you would like to use Alt-Tab shortcut to switch open windows on remote host.
Check following article to enable “Grab keyboard input” that will allow you to use Alt-Tab on remote host: https://kb.nomachine.com/DT09T00267#3.
Consider that you can toggling keyboard grabbing in NoMachine player with Ctrl + Alt + K (default).
Thanks for a good feedback for the version 8.2.
At the moment it’s not possible to use H.264 encoder in NoMachine for the resolutions beyond 4k. We are aware that some hardware encoders now make it possible to use resolutions above 4k and we are working to allow them in the NoMachine.
We cannot provide exact time when this will be available.
There was a typo in the command. Please use
To enable logs
sudo /etc/NX/nxserver --debug --enable all
To collect logs
sudo /etc/NX/nxserver --debug --collect
To disable logs after debug
sudo /etc/NX/nxserver --debug --disable all
Please can you try to use following link
curl -fSL "https://www.nomachine.com/free/arm/64/deb" -o nomachine_arm64.debJuly 18, 2022 at 17:50 in reply to: Are my settings for connecting over the internet ok? #39320
Just a note, NoMachine free has ssh port disabled.
Using a proxy in NoMachine is similar to like using a proxy in Internet browser. If you are using it in your mobile browser, then there is no need to enable proxy functionality in the player connection.
Issue with error 100 and 111 looks definitely related with the port forwarding not correctly set.
As i understood you have in your setup ADSL (router), I will name it after router1, then you have second router and I will name it router2, and then NoMachine server. So your expected connection should work in the following flow:
Mobile ( NoMachine player ) 4G ---> router1 --> router2 --> nxserver
In this situation you will configure port-forwarding twice to be able to be able to access nxserver
[router1 - publicIP:54000] --forwarded to --> [router2 publicIP:54000] --forwarded to --> [ nxserver IP:4000 ]
In my example I mentioned for the router2, the publicIP, is the IP that directly communicates with router1, and as well I used port 54000. You can use other port that is best works for you.