Forum Replies Created
-
Posts
-
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 will make sure it’s 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).
Why does multiple screens affect the number of ports? Do you mean connections/multiple players?
Obviously having a single port in the range would affect the case you run multiple connections from the same client, as only one of them would be able to use UDP. There is also a (small) risk that an external app keeps that port busy.
Hi 4venger, you might be interested in the upcoming NoMachine Network feature in NoMachine 9, coming soon, which will let you see (and connect to) all your computers regardless of the network they are on. By adding them to NoMachine Network, which will be free to do, they will each be allocated a univocal Machine Id. Then all you’ll need to do is log in to the Network service on any device and add your computers to the Machines panel using their Machine Ids (just like you add a NoMachine connection today). There’s a brief introduction about what users can expect (give or take a few small changes): https://www.nomachine.com/network. Connecting to those computers using the Network service will require a Network Subscription, monthly or yearly, and you can continue to use the free version 🙂
Denying rules across the board is planned. In the meantime you can do it using following script:
#!/bin/bash # # CLASS can be one of: all|feature|service|session CLASS=all; if [[ $CLASS = "all" ]]; then CLASS=" -E feature|service|session"; fi; TYPES=$(sudo /etc/NX/nxserver --resourcelist --class $CLASS | grep $CLASS | awk '{print $2}'); for i in $(echo $TYPES); do sudo /etc/NX/nxserver --ruleadd --class propagation --type $i --value no; doneThis script will systematically deny all propagated rules for the specified session class. After which, you can then add the specific, individual rules.
Can you show us the output of the xrandr command so we can check what resolutions are available to you?
When connected to the physical desktop, the maximum resolution you can get is the maximum resolution supported by the remote graphics card i.e the one on the Ubuntu host in your case. More about this is available here: https://kb.nomachine.com/AR02M00835.
You mentioned RDP which works that way because it is a virtual session. If you want to work with a virtual display with NoMachine and a higher resolution, you can try two things:
1) try launching NoMachine’s own framebuffer. So kill X (sudo init 3) and restart nxserver. NoMachine will create its own virtual framebuffer. You should be able to connect and change the resolution.
2) try the NoMachine Workstation. It’s available in the Enterprise section of the download area.
https://www.nomachine.com/product&p=NoMachine%20Workstation