Hello. I’m a relatively new NoMachine user, and I just ran into this issue. I haven’t restarted the Windows system running NoMachine Server, in case there’s anything I can do to help debug this issue.
Hi, indeed a fix was applied in this package, but we needed you to test it in situ so that we could monitor it if it were to happen again. That both of you say the problem has gone is good news. This fix will be officially added to the next release. Thanks everyone for your cooperation!