Britgirl

[Britgirl]

Hi, the client-side logs you submitted show that you are using version 8. Please try updating to the latest v9 on both the client and server sides and tell us if you can reproduce the issue. If you do, we will need to see logs from both sides. Please follow the instructions here: https://kb.nomachine.com/DT08U00298. For the client side logs, please refer to Chapter 1.2 of the same document.

[Britgirl]

Hi, so we checked the logs and there is no issue in the software, rather a broken connection caused by something in your network:

client:

8512 19344 2026-02-12 14:14:49 607.839 ProxySession/ProxySession: 
ERROR! Connection with the remote peer broken.
Error: Connection with the remote peer broken.
Error: Error is 5, 'Input/output error'.

server:

32294 22031 2026-02-12 14:14:50 060.364 ProxySession/ProxySession: 
ERROR! Connection with the remote peer broken.
Error: Connection with the remote peer broken.
Error: Error is 32, 'Broken pipe'.

[Britgirl]

Check your inbox. I’m sending you the download link again, it seems that you are still installing the earlier package we sent you? Remember to reboot the machine after installing. After which you can also add this to the node.cfg file on the target machine, DisplayServerExtraOptions "-gpu 1". This is a new key, not yet enabled by default, which we’ve added and it activates HW acceleration for some operations. It would be interesting to know if there is any difference.

[Britgirl]

Take a look at the following topic: https://forum.nomachine.com/topic/user-for-instant-access#post-52574

I’ll post here for convenience. When you login with your MS account, the following formats are possible:

1) User Principal Name: @ – If you are getting an error, please tell us what error you are seeing when trying to promoted to authenticate on the target Windows machine

2) Down-Level Logon Name: \

3) Short format name, just ‘username’, domain is implicit.

A password is required, your Windows OS PIN is not supported. Please also take a look at the following article which explains in more detail: https://kb.nomachine.com/AR03S01118.

[Britgirl]

You attached the logs for the monitor issue with –eglcapture set to off which means the potential fix for the monitor issue didn’t help, right?

About the logs with –eglcapture enabled, from the logs we see it’s still loading the old library. So do a system reboot and grab new logs, please. Thanks once again.

[Britgirl]

In the meantime we have installed Trixie without any issues. Please, from a terminal on the raspberry device, run uname -m and show us the output, just so that we can be sure that you have the right package.

[Britgirl]

The logs don’t show evident issues within the software, the server closed cleanly. It could possibly be a network problem, but to make sure we need new logs. Set SessionLogClean 0 in the node.cfg file (/usr/NX/etc/node.cfg), reproduce and send the logs.

[Britgirl]

Hi, we’ve sent you a link to a new build. The instructions are the same as before 🙂

1) one set of logs with --eglcapture set to ‘no’ if you are still reproducing the monitor issue. Otherwise, no need for logs.

2) one set of logs with --eglcapture set to ‘yes’ and slowness reproduced.

[Britgirl]

On the macOS machine, you can use the sudo /etc/NX/nxserver --logrotate command in a terminal. Reproduce, then take fresh logs. (see 4.1. Clean-up All Logs in the link above).

[Britgirl]

Can you send us the logs from the machine you are connecting to? You can extract them using the instructions here: 1.1 Server logs – https://kb.nomachine.com/DT08U00298#1.1. You can 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!

[Britgirl]

Hi,

At a glance it could be the wrong package type is installed

What is the output of uname -m on your RPi device?

It might be worth removing the NoMachine package and re-installing.

sudo dpkg --purge nomachine
sudo rm -ef /usr/NX /etc/NX /var/NX

[Britgirl]

The server-side logs were clean. Please try and get them when you are experiencing the issue.

1) Leave log level to Standard.
2) When you reproduce the freezing, take the player logs from the Windows client side. To do that leave the session window open, go to NoMachine settings > Player > Security > Take Logs.
3) Again, when you reproduce the freezing, go also to the server settings > security section on the Mac server host and click Take logs.

When you experience the freezing how is your internet connectivity?

[Britgirl]

Logs received. Thanks!

[Britgirl]

Hi, can you attach the image that you pasted? Use the attach tool below the text box instead of pasting 😉 Thanks.

[Britgirl]

Hi, sorry for the late reply.

Is there a configuration variable that might control a time-out behaviour of the server on MacOS

No, there isn’t.

Are you connecting to them over-IP or are you using NoMachine Network? And what OS are you connecting from? What specific macOS version is on each of the problematic server machines?

Ideally, we would need to see the logs from both sides, client and server sides. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298. Given that you can’t click in the UI on the affected Mac machine to get its logs, we can start with looking at the client logs.

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.

[Author]

Posts