Forum Replies Created
-
Posts
-
The proxy is a NoMachine setting that you enable on the Player side (the machine you connect from), not the server side. You are enabling “Manual proxy configuration” but the message shows that “Failed getting proxy settings” which suggests there is nothing configured in the panel (see attached).
Please show us what you have configured on the Player (open !M on the player, go to settings, select Player, select Security, enable Proxy and then select your preference. You must indicate to NoMachine the details of your proxy server here.)
Attachments:
Ah re-reading I now understand what you were asking. Sorry for the mix-up 🙂 There is no x server running at all on the system you are connecting from, so you are not running XWayland. If this is the case, you are right, the message is not very clear and we decided to change it to something like this:
The NoMachine Player cannot connect to X server
This can be because no X server is running or you didn’t set the DISPLAY environment.
Or it can be because you are running this desktop on Wayland.
The NoMachine Player doesn’t support the Wayland environment without X.
Be sure you run XWayland instead.We’re working on supporting Wayland, natively without XWayland, but it’s not a priority at the moment, so don’t expect this very soon.
The Fn key being stuck is a system bug that was fixed when we moved to the latest macOS API. For the old API it cannot be fixed unfortunately.
NoMachine supports desktops running on Wayland. It installs out-of-the-box just like it does on X.org.
Make sure you always include the “What to include” list that we provide when you are submitting a topic or reply 🙂 What did you install on the server side? I.e the computer you want to connect to. NoMachine Free Edition or maybe NoMachine Workstation?
NoMachine needs a desktop environment running on the machine you want to install it one. What DE are you using? What Linux distro is it, and what version?
Hi thanks for those. After analysis of the logs, it seems no connection is occurring. At this point we need to look at the player side logs. So you should tick the box “Don’t delete log files on exit” in the Player settings (Security), reproduce and then share the .nx folder with us. Thanks!
Hi, Ventura is supported and installs out-of-the-box with default settings exactly the same as other macOS versions 😉
Can’t connect.
To understand why you can’t connect, it would help if knew the error that you are seeing. Can you show us the screenshot of the error that is showing? Or copy and paste the error here.
Our current design supports keys 1:1, so if you want Control on the server-side, you have to press Control on the client as well. We’re currently evaluating ways to customize key bindings by mapping some pre-defined system shortcuts (like Command + C on Mac and Control + C on Windows).
Hi Fritz, sorry I realised that in my reply the
--are not showing in the command.In any case, you need to use the full path to the nxserver e.g
/etc/NX/nxserver/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --debug --enable allreproduce problem and then collect logs
sudo /etc/NX/nxserver/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --debug --collectthen disable
sudo /etc/NX/nxserver/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --debug --disable allWhen did this behaviour start? After a NoMachine update, after a Windows update? Something else?
reset my Windows 11 Pro laptop
What do you mean? Reboot?
I noticed the service wasn’t running, I tried to start it and it seemed to work
Where did you do this? In the Status section? If you restart the nxserver now, what happens?
Is there a tutorial you can point me to, which describes how to setup a redundant NX-Server using two Nodes ?
You should check out the guide for NoMachine Enterprise Terminal Server Cluster, section 3.5. This is the product to choose if you want failover capabilities, and the cluster pair will act as a high-availability gateway to further virtual desktop nodes.
https://kb.nomachine.com/DT09S00251#3.5
The product page: https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Terminal%20Server%20Cluster
Alternatively, you can take a look at the Enterprise Cloud Server Cluster which also offers failover (a clustered pair). This products functions as a HA gateway to any NoMachine server product. This product does not run virtual desktop sessions, you can use it to centralise access to multiple nodes, nodes which support Linux virtual desktops.
More about this product here:https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Cloud%20Server
All our guides are available in the support section of the website: https://www.nomachine.com/all-documents
Is it possible to setup a virtual display which is able to access one or mutliple Nvidia GeForce GTX Titan X to run 3D accel application on top of it ?
To use HW acceleration on your within NoMachine sessions, please consult the following resources:
How to enable H.264 hardware and software encoding/decoding in NoMachine remote desktop sessions
https://kb.nomachine.com/AR10K00706The X11 vector graphics mode in X-Window virtual desktop
https://kb.nomachine.com/AR02L00779How to enable VirtualGL support on Linux in NoMachine v. 6.2 or later
https://kb.nomachine.com/AR05P00982Load-balancing of NoMachine virtual desktop sessions is possible, but not when VirtualGL has been enabled. More about this is here:
Configuring NoMachine to distribute HW encoding workload among GPUs or off-load it to a specific GPU https://kb.nomachine.com/AR11T01179
Thanks for posting your topic and subsequent follow-ups.
NoMachine supports the following Linux distributions: RedHat, Centos, Fedora, OpenSuse/Suse, Debian/Ubuntu, and although ALMA is based on Red Hat, we don’t officially support it. However, that doesn’t mean that it should not work, so we tested the latest version on the fly.
“So I guess then NoMachine is not ready for Alma Linux 9.X ?”
Well, it would appear that Alma Linux is not ready in general ;-)? We downloaded and installed the latest OS version from their website and it would not even install, and only produced Kernel Panic errors.
“I switched to Alma Linux 8.7, which seems to work now, at least if I try to login using a local dummy user. If I try to login using SSSD + LDAP and NFS mounted home I get the following error message creating a virtual desktop:”
Maybe the following resources could be useful:
Connecting with NX protocol to a NoMachine server on Linux in an Active Directory domain
https://kb.nomachine.com/AR12P01007and a very similar problem was reported here:
https://forums.nomachine.com/topic/nx-linux-sssd-ad-issues-with-nfs4-kerberos-home-dir“Looks like the issue can be resolved by disabling SeLinux and Firewalld, even XFCE4 is running. ”
We recently fixed a bug on Red Hat 9, the workaround could be useful maybe?
So looking at the video you made available to us (thanks by the way).
When clicking those items (Restart server, shut down etc) you should see an authentication request dialog. This request is executed by a nxexec process checking credentials. For some reason this dialog is not appearing. Can you check whether clicking the link “Changes disabled” (bottom left) does nothing as well?
If nothing happens when clicking on that link, we would need to check client and nxexec logs from the affected machine.
For logs on macOS, please consult: https://kb.nomachine.com/DT11R00182. Enable logs, try to reproduce the problem and then gather the logs up. Send via email as you did before. Thanks!
Hi, I didn’t say that Firefox was the culprit. We are still investigating an unusual behaviour that we’ve reproduced when initiating the download of and installation of the 64-bit package from the FF browser window, even when the correct NoMachine installation procedure is followed.
I just re-downloaded the .exe with Google Chrome, and the downloaded file is exactly the same
The same file it is indeed, but I don’t know whether you initiated the reinstall of the package by browsing to the appropriate folder using Windows Explorer. So I’m not sure whether you mean the same error occurred.
Either way, a workaround is, whilst we investigate, to download the 32-bit package and install that. Please make sure you follow the correct uninstallation procedure, rebooting where requested, and then follow the correct installation procedure of the 32-bit package, rebooting where requested. Thanks.
There is no special configuration required in order for NoMachine to use HW encoding/decoding as long as the pre-quisites are satisfied. HW and SW encoding work out-of-the-box 🙂
NoMachine supports HW encoding with Nvidia GPU cards provided those cards use the NVENC API. Your Jetson does not support NVENC, so this means NoMachine does not either, and it will revert to SW encoding.
You can find more details about hardware and software encoding in our article here:
How to enable H.264 hardware and software encoding/decoding in NoMachine remote desktop sessions
https://kb.nomachine.com/AR10K00706Hi,
if your device doesn’t support HW encoding or decoding, then NoMachine will use software encoding.
If you have an Nvidia graphics card, NoMachine supports any of the graphics cards that are NVENC-enabled which you see in this list:
https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new
