Forum Replies Created
-
Posts
-
Hi, can you both update to the latest version, 8.14 and tell us if you are still encountering issues? We fixed the following TR https://kb.nomachine.com/TR03U10784 related to the the fallback capture method which fails. We would like to eliminate the possibility that this was affecting your NoMachine set-up. If you are still having issues after the update, new logs would be useful. You can extract them from the server machine using the instructions here: https://kb.nomachine.com/DT07S00243
Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!Our update dialog window should certainly not be blocking access. Can you tell us the macOS version, so we can start an investigation? Also, you mentioned waking your mac up. You can also do that with NoMachine if you are on the same LAN. Have you tried the Wake-on-Lan feature?
We have been unable to reproduce this behaviour. Our own tests show that NoMachine 8.13 works correctly on Ubuntu 24.04. We recently released 8.14 and this includes a fix for a different problem on specific systems with Wayland.
https://kb.nomachine.com/TR03U10784
What we suggest is to update your NoMachine installations first. Does this solve the issue?
If not, please run
sudo /usr/NX/bin/nxserver --eglcapture yesin a terminal, logout from the account on the server and login again, or reboot the system.If there is still no change, a new set of logs would be useful in that case.
Thanks for the feedback and we’ll take it on board to improve communications 🙂
So we’ve gone now from having to use a workaround each time we start NM to a workaround each time we start MacOS. Really hope also this last hurdle will be tackled in a future update.
About this, it seems we are not the only application affected. We are currently awaiting feedback from the Apple developers to understand better why this happens and how we can mitigate it. In the meantime, we made the decision to release the fix we have, with the additional workarounds.
We are not able to reproduce this error. Can we send you debug packages? This would be the current version with additional debug enabled in the logs.
Hi, I don’t see an email from you. Maybe the email is being caught up in our filters? If they are big attachments, they might even be prevented from getting through. Can you try again? Or alternatively, we can download them whichever external service you prefer. Send us the link privately.
Hi, can you submit the following:
i) Windows version on the PC
ii) logs from the client and server sides as well. Enable debug, reproduce then gather the logs and submit. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. There are 4 steps to follow.Submit here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Thanks for reporting. There is a bug that we are aware of related to point 5 in your post. There is a workaround there, so please try that: https://kb.nomachine.com/TR08V11198. For the other issues you are experiencing, we’re investigating.
We’ve released version 8.14. Please update and check the article that we have published in the knowledge base about this fix. https://kb.nomachine.com/TR09V11212
NoMachine 8.14 has been released. Please update your Mac installations via automatic updates or using the NoMachine packages which you can download from our website, and follow the instructions here:
How to connect from macOS 15 with NoMachine Client 8.14 in LAN after a reboot
https://www.nomachine.com/AR09V01251Please start a new thread if you’d like to submit any feedback on this new version.
NoMachine 8.14 has been released. Please update your Mac installations via automatic updates or using the NoMachine packages which you can download from our website, and follow the instructions here:
How to connect from macOS 15 with NoMachine Client 8.14 in LAN after a reboot
https://www.nomachine.com/AR09V01251Are you referring perhaps to a protocol break by separating the web server host from the NoMachine server host? If so, yes this is already possible:
How to configure a NoMachine server to connect web sessions on localhost or on different hosts
https://www.nomachine.com/AR06P00984It’s not clear why you want to uninstall the NoMachine service. Perhaps you can provide us with some more information about what you are trying to achieve. If you prefer, you can contact us privately.
The “nomachine service” item is a shortcut to open Server Status & Settings in the player GUI. The exact same thing can be done from the tray menu, by opening the Server Status, and as well by just starting the player and entering settings.
You can’t uninstall it but you can disable it by disabling the keys EnableServerStatus and EnableServerPreferences in node.cfg which tell the player to not show those panels when the player GUI is opened. So if the user opens the player, clicks the shortcut or the tray menu, the server settings will be never accessible to them.