NoMachine for Linux / Error is 104: Connection reset by peer
Tagged: tumbleweed 104 error
- This topic has 5 replies, 2 voices, and was last updated 1 month, 1 week ago by
hornetster.
-
AuthorPosts
-
April 28, 2026 at 05:03 #55926
hornetsterParticipantBeen using NoMachine for quite a while, successfully, connecting to machines on my local network, from my main machine, as a client.
Have now the need to connect TO my main machine, and am getting the above message. Have tried various things, as in adding ports to the firewall/disable the firewall etc.
Main machine is running Tumbleweed (up-to-date), Plasma (up-to-date), other machines mainly running a form of Ubuntu/Mint.
Logs are here
Did find one similar in the forum, which apparently was fixed by a patch, but that was back in 2019, so would assume this has been included in code, since..
V9.4.14 on all.
Thanks.
April 29, 2026 at 09:41 #55933
hornetsterParticipantJust an update – a Wayland thing, I believe.
Works with X11 version.
Thanks.
May 21, 2026 at 18:16 #56027
BritgirlKeymasterCan you send us the logs from the server side machine? On the server, go to Server > Security > Take logs, save the file and send that to us. You can submit it here or if you prefer, you can send it to forum[at]machine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
May 22, 2026 at 04:53 #56030
hornetsterParticipantHave sent to email (I think…)
Thanks.
June 16, 2026 at 12:00 #56205
BritgirlKeymasterHi, sorry for the delay in coming back to you. Ideally we would need logs with debug enabled to dig deeper. Today, we are going to release 9.7, so what I advise is you update your installation with this new release and if you are still able to reproduce, enable debug (level Debug – 9 in the UI), reproduce and submit new logs.
June 22, 2026 at 12:26 #56220
hornetsterParticipantSorry, have since removed this machine, turns out it was a bit dodgy (in more than 1 way!)
Currently trying to setup a new machine, with 26.04 Gnome Wayland….
Thanks.
-
AuthorPosts
