Forum Replies Created
-
AuthorPosts
-
BritgirlKeymasterYou should disable sound on the server. Set EnableAudio 0 in the node.cfg file. Does that help?
BritgirlKeymasterNot sure what your products is so I’ll point you to one of the Terminal Server v8 guides: https://kb.nomachine.com/DT07T00259#2.3. You’ll find all the v9 guides on our support page 😉 https://www.nomachine.com/support/documents
You can also refer to this article https://knowledgebase.nomachine.com/AR10K00698
BritgirlKeymasterIt sounds more like something is broken on the system OS. There are references in logs to ‘/run/user/60578/’ so this directory has to be present. Maybe you could investigate the user with uid 60578?
BritgirlKeymasterNo, but in the upcoming version 10, when you publish a machine to NoMachine Network, and are logged in while doing so, it will be automatically added to your Machines book. Can this be helpful to you?
BritgirlKeymasterHi,
On Enterprise software it is still possible to add machines to NoMachine Network even if the license has not been activated yet.
Do you receive an error message? Can you go to the Server settings > Security and click Take logs? Please submit these.Also tell us:
– version of NoMachine software
– which specific product you installed
– did you try a reboot after installation?
– can you tell us if in Settings > Server > Security the server is showing as running?Activating the license can be done by following the instructions here, skip straight to “How to install the license”: https://kb.nomachine.com/AR10U01206#3
If you have a full Enterprise subscription, please consider opening a support enquiry (you can do this from your User Area) because some of the details that we ask you could mean showing sensitive information. For this reason, your image has been removed from this topic.
BritgirlKeymasterHi, server logs would be useful. Go to the NoMachine server settings on the Zorin OS >Â Security > Enable debug in the logs, restart, reproduce, collect and share logs with us. You can attach them here or send directly to forum@nomachine.com (make sure to use the title of this topic as the subject of your email).
May 15, 2026 at 16:27 in reply to: Black screen / Error 108 connecting to Pop!OS 24.04 COSMIC (Wayland) #55981
BritgirlKeymasterHi, thanks for your report. It’s a known issue and there is a Trouble Report open describing the problem. Use the following link to track its status: https://kb.nomachine.com/TR01X11700.
BritgirlKeymasterWhen you reproduce the problem, can you send us the logs from the device you are connecting from? See the following document for instructions: https://kb.nomachine.com/DT08U00299#2. You can attach them here or, if you prefer, send them to forum[at]nomachine[dot]com using the topic’s title as the subject.
After you’ve done that, try disabling hardware decoding on the client side. Inside the session, bring up the menu (Ctrl+Alt+0 or click on the page peel at the top right corner of the window). Then click on Display -> Change settings. In that panel click on the Modify button to open the advanced display settings. Click on ‘Disable client side hardware decoding’ to disable it. Does this change anything?
May 12, 2026 at 08:35 in reply to: “Show main window” and “Show server status” buttons do not work #55970
BritgirlKeymasterHi, can you tell us what version of NoMachine it is? And what version of Windows?
BritgirlKeymasterHi,
thanks for submitting the logs. It appears there is something wrong with the ‘gdm-greeter’ system user that is used for the login. The
debug --collectthat is in our logs procedure did not find your home directory and so we have no logs from there. You will need to gather them manually.By default on Ubuntu 26.04 the home directory should be in
/run/gdm3/home/gdm-greeter/. But since something is wrong they might be in another place. The command:echo ~gdm-greetershould point to them. We need the whole .nx directory that you find there. Zip that up and send as before 🙂
Can you also tell us if this is a fresh install or is it an update from another version. If it’s the latter, what version were you updating from? Also useful is any journalctl output from the last boot:
journalctl -b -1 > journal.log
BritgirlKeymasterCan you tell us what desktop environment you are connecting to? Logs from the Ubuntu machine would be useful as well. Go to the NoMachine settings on the Ubtunu server, security -> log level debug, restart, reproduce the problem, collect the logs (Take logs from the same Security panel) and share them with us. You can attach here or send directly to forum[at]nomachine[dot]com. In the case of the latter, please use the title of this topic as the subject of your email. Thanks.
BritgirlKeymasterHi, we have a release candidate for all users experiencing the issue reported in this topic. If you’d like to try it, please contact us.
April 23, 2026 at 10:27 in reply to: After disconnect, physical screen always stays black (on 9.3.7) #55916
BritgirlKeymasterrbuehlma, would you be interested in installing a debug library? If you are, we will send you a separate email with further instructions.
BritgirlKeymasterNo 🙂 If one connection over the Network service is sufficient, purchase a Network Personal Subscription. The name does not limit it to “personal use” only. If you are a company that wants to use the NoMachine Network service, you can choose from any of the Network subscriptions available. Choose according to your NoMachine Network connection needs.
BritgirlKeymaster– Personal – for personal use
– Business – for business usageA NoMachine Network Personal Subscription or a NoMachine Network Business Subscription. You choose for each user what works best for them 🙂 The Network Business Subscription will allow more concurrent Network connections from the same device.
-
AuthorPosts
