Forum Replies Created
December 22, 2022 at 22:47 in reply to: Text display issue on Mac M1 #42111
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.December 22, 2022 at 16:46 in reply to: Keyboard shortcut to cycle through windows #42103
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).December 22, 2022 at 16:35 in reply to: Using H.264 beyond 4K #42102
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.November 28, 2022 at 11:24 in reply to: Can’t connect thru internet #41685
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 allSeptember 5, 2022 at 13:40 in reply to: Cannot install NoMachine #40037
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.July 15, 2022 at 18:27 in reply to: Manjaro -> Ubuntu connection problem #39275
Can you please execute some commands to collect core stack and send it to us
You will receive an output like this:
TIME PID UID GID SIG COREFILE EXE SIZE Thu 2022-07-15 19:48:13 CEST 120316 1000 1000 SIGSEGV present /usr/NX/bin/nxplayer.bin 2.1M
then depending on the pid number of the nxplayer crash, please execute:
coredumpctl gdb 120316 --debugger-arguments="-batch -ex 'thread apply all bt'" > /tmp/crashReport.txt
then please send us /tmp/crashReport.txt crash report file.June 28, 2022 at 17:31 in reply to: Error 102 over IPv6 when connecting to Windows 7 #39042
Can you verify if you did correctly enable IPv6 on the Windows XP?June 11, 2022 at 11:00 in reply to: New version of Manjaro GNOME not compatible with NoMachine #38840
I am glad that you solved the problem.June 9, 2022 at 10:43 in reply to: New version of Manjaro GNOME not compatible with NoMachine #38829
Sorry for the delay. Can you explain further what you mean with ‘I had a little progress’? As far as we know, with that extension, everything should work even after logging out from the desktop.
That said, even without the extension, NoMachine should work by using an alternative method to capture the screen. We found a bug in this method that affects your case and it will be fixed in the next NoMachine version.May 18, 2022 at 12:51 in reply to: New version of Manjaro GNOME not compatible with NoMachine #38654
if you are using Wayland, can you try to disable it?May 17, 2022 at 16:09 in reply to: New version of Manjaro GNOME not compatible with NoMachine #38647
Can you tell me if you have problem with lock screen when using physical or virtual desktop?May 10, 2022 at 15:59 in reply to: Run script after connection and after disconnection #38590
Please just add your scripts in the node.cfg file, and it will be executed with current logged user.