- This topic has 36 replies, 8 voices, and was last updated 3 hours, 47 minutes ago by
.
-
Posts
-
Same here after upgrading my server from 22.04.4 to 24.04.1 LTS. Both client and server working on latest nomachine_8.13.1_1_amd64.deb, after upgrade getting (Error is 104: Connection reset by peer.)
Tried today connecting from a fresh install on a totally separate Windows 11 box as the client. Same results, control but no video, consistent through all three possible values of ”Enable hardware accelerated decoding”.
To me this strongly suggests server rather than client side problems. No response here since I last uploaded server logs on 12 September.
psantucc
we’re unable to reproduce this behaviour despite several attempts and the logs you sent us indicate nothing strange.
1) can you tell us if the server is headless?
2) send us all the logs in this directory: $HOME/.nx/nxegl/
morozov, is your server headless? Enable debug and send us the full logs. Please follow the instructions here: https://kb.nomachine.com/DT07S00243
Also send us the logs in the directory in point 2 above.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, thanks for quick support response.
Ok, upgraded Ubuntu 24.04.1 works as server but runs standard Ubuntu 64 bit desktop. I have NoMachine free version installed on few desktops and connect to each one at the time (all running standard Ubuntu 22.04.4 desktop with latest version of NoMachine server except one mentioned above latest NoMachine server but upgraded to Ubuntu 24.04.1 as a pilot test). First time failed to connect to upgraded machine using nomachine I have reinstall it on both server and client and following similar connection failure change on client (running 64 bit Ubuntu 22.04.4 Gnome) <option key=”Enable hardware accelerated decoding” value=”false” />. I have tried to connect to 24.04.1 server from other desktops and got same error message.In the attachment logs from server
Regards
morozov
My server is not headless either. Full bog-standard Ubuntu GNOME desktop environment. The physical display is usually turned off, but I’ve had it both off and on for these recent tests. That’s how I can tell I’m getting keyboard and mouse control even though my client window is black.
Logs from $HOME/.nx/nxegl/ are attached, since they are small enough.
I have the same issue. Ubuntu 24.04.01 server (with hardware dummy display stick) and Windows 10 player.
Niether changing the hardware accelerated decoding option nor upgrading nx from 8.13.1 to 8.14.2 made a difference.
We have been unable to reproduce this behaviour. Our own tests show that NoMachine 8.13 works correctly on Ubuntu 24.04. We recently released 8.14 and this includes a fix for a different problem on specific systems with Wayland.
https://kb.nomachine.com/TR03U10784
What we suggest is to update your NoMachine installations first. Does this solve the issue?
If not, please run
sudo /usr/NX/bin/nxserver --eglcapture yesin a terminal, logout from the account on the server and login again, or reboot the system.If there is still no change, a new set of logs would be useful in that case.
Have tried new version 8.14.2 on both (client w/Ubuntu 20.04.1 and server w/Ubuntu 24.04.1). Working stable. Thanks
Sad to report no change in my symptoms after updating clients and server to 8.14.2, setting
--eglcapture yesand restarting the computers.nxegl logs are attached.
FWIW, I do appreciate the effort spent on what is clearly a corner case of an unpaid user.
We need debug logs like before. I’ll paste the link to the instructions for convenience, https://kb.nomachine.com/DT07S00243. Enable debug, reproduce, zip up and send them to forum[at]nomachine[dot]com or attach them here.
You must be logged in to reply to this topic. Please login here.