Connection reset by peer

Roon Core Machine

Lenovo X1 Carbon Gen 3 with Ubuntu 20.04.3 freshly installed.
Intel i7, 8GB of RAM, SSD disk.

Networking Gear & Setup Details

Endpoint is wired to modem, Roon Server (running on the above Ubunut) is wired to modem, Remote app is on Android phone.

Connected Audio Devices

The only endpoint is a Raspberry Pi 4B running Roopie.

Number of Tracks in Library

No idea, but this is (very very) likely not the issue. Read below :slight_smile:

Description of Issue

Roon Server installed fine on Ubuntu. I am well versed in Linux, and with systemd I see the roonserver service running OK after it is restarted. But then I open up the app, maybe play a (Tidal) track, or not. In any case, after some minutes, the app says that it can’t connect. I go check with ‘sudo systemd status roonserver.service’ and what I see is:

● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-10-04 22:20:53 CEST; 51min ago
Main PID: 160260 (start.sh)
Tasks: 97 (limit: 9102)
Memory: 1.8G
CGroup: /system.slice/roonserver.service
├─160260 /bin/bash /opt/RoonServer/start.sh
├─160264 /opt/RoonServer/RoonMono/bin/RoonServer --debug --gc=sgen --server RoonServer.exe
├─160276 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=33799
├─160282 /opt/RoonServer/Server/processreaper 160276
└─160317 /opt/RoonServer/RoonMono/bin/RAATServer --debug --gc=sgen --server RAATServer.exe

Okt 04 22:29:54 streamer start.sh[160276]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Okt 04 22:29:54 streamer start.sh[160276]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <9f7747ca7df742bc9cc8f94c1fafe024>:0
Okt 04 22:29:54 streamer start.sh[160276]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in <11073c9a2e2d4614af4b2a7f4d419d45>:0
Okt 04 23:00:12 streamer start.sh[160276]: [AAC/oop] GOT 44100/24/2 10839 samples mf=0x7f8d000432e0 underlying_objecttype=-1 underlying_sfidx=-1
Okt 04 23:02:18 streamer start.sh[160276]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Okt 04 23:02:18 streamer start.sh[160276]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <9f7747ca7df742bc9cc8f94c1fafe024>:0
Okt 04 23:02:18 streamer start.sh[160276]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in <11073c9a2e2d4614af4b2a7f4d419d45>:0
Okt 04 23:06:33 streamer start.sh[160276]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Okt 04 23:06:33 streamer start.sh[160276]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <9f7747ca7df742bc9cc8f94c1fafe024>:0
Okt 04 23:06:33 streamer start.sh[160276]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in <11073c9a2e2d4614af4b2a7f4d419d45>:0

The offending part is likely the “connection reset by peer”. I have gone through the following multiple times by now: restart roon with systemd / connect with phone app / stuff is working, play some music, or not, wait a bit / phone goes to sleep → wake it up, check app: “can’t connect” / go check roon status with systemd: above error.

I really want to love Roon. I’m on free trial now. If this gets resolved I’ll definitely pay for it but if it doesn’t I just can’t see myself going through the above multiple times a day.

Any help is appreciated!

Cheers.

EDIT: it seems my VPN, which was set to “allow lan traffic” but otherwise was running system wide, was causing the issue. (this is not the trivial mistake though, I mean LAN traffic does work with the corresponding option checked in the VPN). Now I have removed that, and instead I did a split tunnel config whereby all apps except a blacklist are bypassing the VPN. It seems to be better. I will update in the coming days.

Hi @Gustavo_Lucena_Gomez and welcome to the forum.

Maybe another one suffering from issues with NetworkManager:

1 Like

I see. Thanks. But are you sure this is the issue in my case? Is there a way I can make sure.

And of course, I have no choice but to voice my disappointment at this. Ubuntu is stated to be the most supported of all Linux distros for Roon.

Thanks anyway!

The world is changing. First Debian was in demand, then Ubuntu conquered the desktop, then came Linux Mint based on Ubuntu, was overtaken by Manjaro (Arch-based). PopOS! based on Debian was in focus for a while and now other distributions are storming forward again.

The fan of Debian, Arch, Slackware will never be unaffected by this. In the corporate environment Fedora or Suse are still in demand and the will to change always comes only with longer unsolved problems.

I also switched from Linux Mint to Manjaro because of Roon and KDE. But I’m still trying to make peace with Debian. It is still too much terminal for many beginners, what old Linux connoisseurs love. Perhaps there are even older users who complain that much is hidden behind a colorful desktop cumbersome. Beginners find that better.

I get your point, and that is fair enough. However, my initial statement remains true: Ubuntu is stated (by Roon themselves) to be the most supported distro. As such, these problems are disappointing.

Sorry but no. How should I? You are the one with a problem. I guess it’s up to you to figure out if the solution(s) from the thread I linked also help you to resolve your problem. If yes then I think it’s confirmed that this was the issue in your case too.

1 Like

Hey @Gustavo_Lucena_Gomez,

Thank you so much for choosing to connect on the Roon community forum to find a resolution for this issue. We’re very sorry it took us this long to get back to you…

In the meantime, it looks like friendly subscribers, like @BlackJack and @Uwe_Albrecht, have chimed in to help. Thank you both.

I was wondering if there are any relevant updates you could share with us. If there’s anything we can help with at this point, it’d be our pleasure to lend a hand :nerd_face:

Hey there @beka

Sorry, I did mean to get back to you guys. It’s been working flawlessly but I changed two things so I am unsure which one caused the problem (I changed my VPN settings and also changed the network manager). I guess I’ll troubleshoot a bit more when I have more time.

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.