Forum Replies Created
-
Posts
-
Saving credentials must be done during session start. Not all session parameters can be configured before starting a connection because some require handshaking with the server, including credentials. There is no save button in the Edit panel, so any changes you make there are automatically saved, when you hit the back arrow.
To save the credentials you should add the connection first, then start the connection, insert the system account credentials when requested and tick the box for saving credentials, and connect. You must complete the connection to the remote desktop, then you can close the connection. After which you can export the nxs file by using ‘Copy file’ (right click on the session icon in Machines and select Copy file, then select what to name it and where to save it).
Bear in mind that Sway is not fully supported yet. Can you tell us whether the graphics drivers are proprietary or open source? And are you running the Ubuntu system in a VM? Can you also submit logs from the Ubuntu host? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Custom scripts are placed in the server.cfg or node.cfg on the nodes of the cloud server. If you’re looking for a way to avoid accessing each node to configure the cfg files, you could probably run a normal script. But this looks very product specific and beyond the scope of these forums, you should reach out using the contact us link in the footer and select “General enquiries”and your request for help will be forwarded on to the support/pre-sales team.
Sorry, my bad, I wrote desktop environment but meant “distro”. As I said, we tested on the fly on ARCH and there were no problems. What distribution are you using?
Hi, so we checked this app. The issue is not in NoMachine. Some googling came up with:
Issue Description After updating to MacOS Sonoma 14.5, KeepassXC no longer functions properly. When attempting to open the application, the database unlock window fails to display….
https://github.com/keepassxreboot/keepassxc/issues/10757
Run this:
do shell script "/Applications/KeePassXC.app/Contents/MacOS/KeePassXC --allow-screencapture &>/dev/null &"and that should fix the problem.
Have you tried the packages from our website? We tested on the fly with Hyprland on Arch and didn’t have any issues, but please download the official packages from nomachine.com. If you are having issues, please tell us what desktop environment is running on Hyprland.
The OS versions would be useful to know btw.
The login to the server always supports credentials saving, so why you are not seeing it needs to be investigated.
With regards to the balloon notification, it is normal to see this pop up – it functions as a security notification to tell the user who is front of the desktop that a user wants to connect so that you can accept or refuse. Why you are seeing “user1 is …..” when you are actually connecting as user2 is wrong behaviour, and so this also needs further investigation.
So, we need:
– screenshot/s of the NoMachine panels when you are logging in
– screenshot/s of the balloon notification that appears when you are logging in with User2 to the Mac desktop
– logs from the Mac server
– logs from the Windows machine
To get both of these logs, please follow the instructions here: https://kb.nomachine.com/DT07S00243. Steps 1 – 3 are for the server side, the Step 4 is for the device you are connecting from.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Indeed the rules that can be propagated from the Cloud Server to its nodes are those listed in the guide. We can check if it can be updated.
The command ‘
nxserver --resourcelist‘ lists all the resources of the host where command is run (not necessarily that can be associated to a rule). Those resources with value yes, are available on that machine. If a profile rule denies a resource, its value will become no.Hi, this is a known issue. Please use the link to monitor its status, the link also contains a workaround.
Black screen when connecting to Wayland using two monitors
https://kb.nomachine.com/TR0110731Hi, did you mean to submit a screenshot?
Anyway, NoMachine doesn’t have an option to choose the GPU, it uses the GPU that is set by default in Windows.
Did you try to select a different GPU in Windows settings?
On Windows 10 and 11:
– click on the Windows menu and select ‘Settings’
– go to System -> Display -> Graphics.
– in Custom options for apps select Desktop app and click ‘Browse’
– go to the directory where NoMachine is installed and move to ‘bin’ folder.
– Type nxplayer.bin in the ‘File name’ field at the bottom of the panel to find it.
– Click on Add to add nxplayer.bin to the list. (Window lists only .exe files, nxplayer.bin is not visible by default).
– select nxplayer.bin and open Options
– you can then select in Graphics preference the GPU you want to use for nxplayer.binThey are rather large. After sending them you can disable debug and remove them.
Logs contain usernames and IP addresses and this information can be removed beforehand if you prefer to do that before sending. I can send you the details via email to upload to the NoMachine Support log service we have for subscribed customers (read more about our privacy policy here https://kb.nomachine.com/AR05P00977 and how logs are handled).