Forum Replies Created
-
Posts
-
Thanks to your team for this awesome fast support. Everything is working again.
Have a nice time!
Bernd
.. sorry. got an answer an few minutes later
The problem does not exist as long as I connect via [removed] at the same time! It will appear again once I am not connected with a [removed] Server additionally…
Well, I hope the logs will help.
Therefore, workaround is still using [removed]-Connection to help NX-connection 😉
@britgirl: I did as requested and sent the log.
@brian, nxmac : can you reproduce the strange behavior that happened when I switched the log level as described below? :1. I switched to log level 9 and hit “restart server” in the GUI.
– I tried to reproduce, but was not able to anymore. Killing the connection and connect again was possible without any issue.
2. I switched back to log level 6 and hit “restart server”.
– Voila – the problem was back again.
3. I switched to level 9 the second and restarted the server
– Reconnecting was possible 2-3 time without problem, then the problem appeared but in difference to log level 6, the white screen got away after 20-30 seconds and I saw my remote screen. There was no “connection was reset ” message anymore.
Best
Bernd
(bloody)workaround:
Start VNC screensharing via terminal and use a VNC-Client to connect.
Stop NoMachine in Finder menu completely.
Start the app and within the app, start the server again.
-> NoMachine will work again. At least for me. To check back, I broke down my connection without logout/closing the nomachine-window. The issue was up again after re-establing my connection. I got the white screen..
I do not understand, why this is helping, but a restart of nxserver/nxd on commandline do not help…
Have exactly the same issue. Server running on M1 Machine.
I got a screen succesfully one time after reboot of the server machine. Once the connection dropped out for any reason, a login show the white screen and the error message after a while.
restarting nxserver via commandline did no solved it.
Everything was without issue before update.