Forum Replies Created
-
Posts
-
Hi, please note that we always recommend downloading packages from our website because we are not responsible for packages that users download from external repositories. Our download section always provides the most recent version for reasons explained in the article here: https://kb.nomachine.com/AR08C00250.
Our developers are currently working on a fix, the release of which should be in the next maintenance. We can of course provide an earlier version which is not affected until then. Please reach out to us through the website with your request and we will provide you with a private link to download.
Hi, are you able to send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1.1, by clicking Take logs in Settings > Server > Security. For the moment, no specific debug level is required.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, are you able to send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1.1. On the server machine you are connecting to set the log level to 7, reproduce and then “take logs”,
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
You could update your environment maybe. NoMachine 9 was recently released. We also made a version 8 (8.18) update today for subscribed customers. Fra81 suggested it might be specific to your system, and for such a specific problem, the forum is not the right place to get the assistance you need. Instead, a thorough investigation can be handled through the support channel.
Let’s make a quick recap because the beginning of the topic is from May and we are now in July. Just to be clear for those reading, the free version of NoMachine is absolutely free and does not need to be “renewed”, nor should there be any message about using an expired evaluation when you have installed it. Just to be extra sure, can you confirm you downloaded and freshly installed a package from this page? https://download.nomachine.com/download/?id=3&platform=windows after having completely uninstalled the previous package?
Hi Basstie and Serqetry, we have sent you a package to test. It contains a potential fix. So please install and let us know if the problem is solved. If you can still reproduce it, please submit the logs. Instructions are in my email. Thanks!
Hi, our records now show that the 2FA pairing has taken place and is working. You can disable debug and now enjoy 2FA 🙂
We have opened a Trouble Report for this issue. Please track its status with the following link: https://kb.nomachine.com/TR07W11484.
The logs show a possible issue with permissions. Please follow the instructions here to get further verbose logs from the server machine you are connecting to: https://kb.nomachine.com/DT08U00298#2 from the CLI. Restart the server before reproducing the issue and then resubmit. Thank you!
I previously wrote to start the connection, it is not necessary. So follow these corrected steps. Sorry for any confusion.
– Remove/disable 2FA for the connection on the NoMachine macOS side (Settings > Network > Machine > Two-factor, Change, remove the tick from “require 2FA” box, remove the User Id from the box, click Apply)
– Enable level 9 in Server > Security > Logs and restart the server.
– Enable 2FA for the connection again in Network (Settings > Network > Machine > Two-factor, Change, tick the “require 2FA” box), insert the User Id/NoMachine account, click Apply.
– What should appear is the push-notification I’ve attached (there’s a short version, and then the long version (attached) when you click on the short version).
– Go back to Server > Security and click Take logs. Save and send to us.Thanks for those, I was just about to come and ask you to send them. We’ll take a look and come back to you.
Hi Brian
we got your images and additional info, thanks for that. Something is happening, but our own debugging has not reproduced, so we need the logs from the mac mini server 🙂
– Remove/disable 2FA for the connection on the NoMachine macOS side (Settings > Network > Machine > Two-factor, Change, remove the tick from “require 2FA” box, remove the User Id from the box, click Apply)
– Enable level 9 in Server > Security > Logs and restart the server.
– Enable 2FA for the connection again in Network (Settings > Network > Machine > Two-factor, Change, tick the “require 2FA” box), insert the User Id/NoMachine account, click Apply.
– What should appear is the push-notification I’ve attached (there’s a short version, and then the long version (attached) when you click on the short version).
– Go back to Server > Security and click Take logs. Save and send to us.Attachments:
A Trouble Report has been opened and you can track its status using the following link: https://kb.nomachine.com/TR04V11133.
It’s reproducible when using Wayland, and there are some limitations with remote cursor tracking on Wayland. Please check this article https://kb.nomachine.com/AR02P00969, in the known limitations section. As a workaround you can try disabling Wayland.
