Black screen on connect after 8.15.3 upgrade

[Brian]

Running a MacMini 2020 with M1 chip. Working flawlessly until installing the most recent Mac update (8.15.3). Now upon successful connect to the host computer, the client (iPhone running NM v. 8.7.1) onnects with black screen. I can see the computer on the local LAN and I have an external connection to the machine via IP address, both of which have historically connected without exception to the MacMini host. The only change is the fact that the upgrade was installed on the MacMini. Does anyone else experience the same or have a solution at all?

Further info: On the MacMini host that was showing black screen to the iPhone client when attempting to connect: the black screen on the iPhone client appears when the MacMini host display has gone to sleep. The MacMini settings in energy are set to keep the computer from going to sleep when the display goes to sleep.

If a connection is attempted while the screen is awake, everything works normally.

This behavior is a change since the 8.15.3 update. No settings or any other changes were made on this computer, which was connecting fine before the update was installed. It also seems to be specific to the MacMini with the M1 processor, as I have also installed the update on my MacBook Pro (Intel CPU) and there have been no changes to it performing satisfactorily as it was before the update was installed. Hopefully this helps.

Thanks!

Brian

[bucu]

Hi,
can you edit /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg on your mac mini and add this line:
DisplayServerExtraOptions "-nosckgrab", then restart NoMachine (sudo /etc/NX/nxserver --restart) and try to reproduce?

If it’s possible it would be good to know if the problem exists in the desktop version on NoMachine as the client when connecting to that mac mini.

[Brian]

No luck with this. I unlocked the app and edited the cfg file as directed and restarted the server at the command line but the results are unchanged. The client reports and error 5: input/output error- “could not start the display server” after disconnecting from the black screen…I will go back into node.cfg and edit the added line back out I guess? What’s next (?)

[nxmac]

I normally connect to my M1 mini from a Windows desktop, but when trying to connect from my iPhone on Saturday, I was also experiencing OP’s issue.  If I left it sitting on the black screen, I would get disconnected before long.  I don’t experience this exact issue when I connect from the Windows desktop, but I do experience something similar, a white screen and a disconnect before long.  I have been connecting via SSH and restarting nxserver each day when this happens since upgrading NoMachine, and sometimes that doesn’t solve it and I have to connect via VNC to restart the service via the NoMachine GUI.

I also started noticing WindowServer crashes on macOS since upgrading to this version of NoMachine.  I didn’t make the connection with those crashes and this upgrade until one happened while I was connected today (which lead me to check forums to see if others were having issues), as I was assuming maybe a restart would solve them.  However, I was connected and active when WindowServer crashed today.  When it crashed, NoMachine indicated that I needed to re-authenticate because the desktop owner had changed.  After authenticating, I was also prompted for an admin login by NoMachine.  After putting that in, I as able to log in to the desktop again, and I could see the same crash report screen I have been seeing daily.

[Brian]

PS when I get home I will attempt to connect to the Mac mini from another desktop for you after having made the edit to the cfg file and will report my findings …

[Brian]

When connecting from another desktop (actually a MacBook Pro running the same software version of MacOS Sequoia as the MacMini, I get the following results (screenshots attached:)

1 – Two connections on NM player for this same MacMini: one for the LAN connection and the other using the external IP for on the road.

2 – Connecting with LAN connection yields a white screen

3 – Connecting with external IP address connection produces white screen (shot #4) and then shows a “Connection Reset By Peer” error (shot #3) which alternates on and off every ten seconds or so on top of the white screen.

This is with the mod to the node.cfg file edited in as requested above.

 

Attachments:

1. 

   Screenshot-2025-01-20-at-16.43.07.png
   

2. 

   Screenshot-2025-01-20-at-16.43.45.png
   

3. 

   Screenshot-2025-01-20-at-16.44.52.png
   

4. 

   Screenshot-2025-01-20-at-16.49.01.png
   

[Author]

Posts