Roon 1.8 880 running in Proxmox container (Ubuntu 20.04.2 LTS)
Intel i5-10400 (4 cores, 4GB for VM)
All OS updates installed
Networking Gear & Setup Details
OPNsense firewall vitualized in Proxmox (Roon core on VLAN 100, clients on VLANs 10 and 30)
Proxmox connected over fiber to Netgear MS510TX
Clients connected to Netgear GS110EMX and Ubiquiti AP WiFi 6 Long-Range
Connected Audio Devices
Naim Uniti Atom
Win 11 desktop with Topping D10s
Apple iPad
Samsung Galaxy A50
Number of Tracks in Library
25.000 tracks
Description of Issue
Connection failed after update to 880
Rollback to previous version solves the problem
Since the update to 880 clients would no longer connect to the Roon Core.
After some investigation on the side of the Proxmox firewall, following entries were present:
201 7 veth201i0-IN 16/Dec/2021:09:18:52 +0100 DROP: IN=fwbr201i0 OUT=fwbr201i0 PHYSIN=fwln201o0 PHYSOUT=veth201i0 MAC=xxxxx SRC=192.168.10.173 DST=192.168.100.80 LEN=52 TOS=0x00 PREC=0x00 TTL=127 ID=12432 DF PROTO=TCP SPT=31089 DPT=9330 SEQ=197902906 ACK=0 WINDOW=64240 SYN
201 7 veth201i0-IN 16/Dec/2021:08:56:47 +0100 DROP: IN=fwbr201i0 OUT=fwbr201i0 PHYSIN=fwln201o0 PHYSOUT=veth201i0 MAC=xxxxx SRC=192.168.10.173 DST=192.168.100.80 LEN=52 TOS=0x00 PREC=0x00 TTL=127 ID=11069 DF PROTO=TCP SPT=30080 DPT=9332 SEQ=2537644595 ACK=0 WINDOW=64240 SYN
After allowing incoming TCP traffic on both these ports, it is possible again to connect.
If Iām correct, there is no mention of any of these ports in the documentation.
when an 8th Sonos device is enabled it perhaps tries to create a listening socket on one of the ports already in use (hence āaddress already in useā). Maybe it is mistakenly trying to use the 9330-9332 range? I donāt know which port it is attempting to listen on
So is the expected solution for me to open ports, or for me to disable Sonos zones to get under the ā7 Sonos zone capā or for Roon to fix something? Right now have disabled a few Sonos zones, which is fine for now. Thanks so much for diagnosing.
āWe just use some random ports and our users just have to figure out for themselves which ones they areā ?
Every piece of software that uses network protocols has documentation where you can find what ports are being used, but Roon doesnāt?
Iām sorry, but this is unacceptable!
If you canāt provide this kind of technical data, this will be the last year I subscribe to Roon.
Had some time to do a little more digging this morningā¦
For people having issues with Chromecast no longer functioning, Roon now uses port 9333 to stream to my Nest Mini.
I noticed on my firewall that these connections were being blocked:
192.168.30.101:50584 192.168.100.80:9333 tcp Default deny rule
Allowing 9333 to pass through and opening the port on my Core solved the Chromecast issue.
Maybe extra ports are being used if you stream to multiple Chromecast devices, but I canāt tell for sure.
Some simple documentation around the ports being used would have saved us users hours of frustration and digging around logsā¦
Do I suffer from the same?
Since 880 I get strange restarts:
root@scarpe:/var/roon/RoonServer/Logs# journalctl -u roonserver.service -f
-- Logs begin at Tue 2019-02-26 20:44:22 CET. --
dec 17 15:37:40 scarpe start.sh[3499]: Started
dec 17 15:37:40 scarpe start.sh[3499]: aac_fixed decoder found, checking libavcodec version...
dec 17 15:37:40 scarpe start.sh[3499]: has mp3float: 1, aac_fixed: 1
dec 17 15:37:45 scarpe start.sh[3499]: Running
dec 17 15:56:12 scarpe start.sh[3499]: Error
dec 17 15:56:14 scarpe start.sh[3499]: Initializing
dec 17 15:56:14 scarpe start.sh[3499]: Started
dec 17 15:56:14 scarpe start.sh[3499]: aac_fixed decoder found, checking libavcodec version...
dec 17 15:56:14 scarpe start.sh[3499]: has mp3float: 1, aac_fixed: 1
dec 17 15:56:18 scarpe start.sh[3499]: Running
The open files of the RoonAppliance process grows massive and fast:
root@scarpe:/var/roon/RoonServer/Logs# ls -1 /proc/$(pidof RoonAppliance)/fd | wc -l
1321
root@scarpe:/var/roon/RoonServer/Logs#
root@scarpe:/var/roon/RoonServer/Logs#
root@scarpe:/var/roon/RoonServer/Logs# ls -1 /proc/$(pidof RoonAppliance)/fd | wc -l
1470
root@scarpe:/var/roon/RoonServer/Logs# ls -1 /proc/$(pidof RoonAppliance)/fd | wc -l
1517
root@scarpe:/var/roon/RoonServer/Logs# ls -1 /proc/$(pidof RoonAppliance)/fd | wc -l
5372
Lots of:
12/17 15:58:25 Critical: scx: in OnExit: System.Net.Sockets.SocketException (98): Address already in use
at Sooloos.Http.HttpServer._Start()
at Sooloos.Broker.Transport.CastZonePlayer..ctor(State state, IEnumerable`1 realeps, IEnumerable`1 endpoints)
at Sooloos.Broker.Transport.ZonePlayerFactory.Create(State state, IEnumerable`1 endpoints)
at Sooloos.Broker.Transport.Zone.LL_UpdateEndpoints(Boolean first)
at Sooloos.Broker.Transport.Zone..ctor(State state, Module module, Sooid zoneid, IEnumerable`1 endpoints)
at Sooloos.Broker.Transport.Module.ev_threadexit()
at Sooloos.SynchronizationContextThread.OnExit()
And after a while:
RoonServer_log.20.txt:12/17 14:41:36 Debug: NotifyCorruptZoneDatabases Exception LevelDb.Exception: IO error: /var/roon/RoonServer/Database/Core/5d5b0749cc6e455194aca11ab9ed0c4d/transport/zone_16015a8849ba9e0f538753043adb67708409.db/CURRENT: Too many open files
I never used iptables or other FWs on my core. Never had these kinds of issues before the upgrade.
It just seems seriously broken.
I donāt think itās related, Iāve checked my logs and Roon never crashed.
My remotes started working right away as I opened the necessary ports on my firewall
For posterity, and if anyone with similar problems should find this post:
Iāve been able to narrow down the ports my setup uses to tcp 9330:9339 and udp 1900,9003. If you want chromecast to work, it seems youāll also have to open tcp 8008,8009 and udp 32768:65535
Opening these fixed all connection issues for me.
Hopefully Roon doesnāt pull some different port numbers out of itās hat with every new releaseā¦
Does it still work with Roon 1.8 build 882?
Here Chromecast audio was working fine with firewall rules. Now updated to build 882 when I hit play, it wonātā¦ when I disable the firewall it works. Looks like a new port to add?
Hi @Ramon_Laponder , you seem to be correct.
Iāve updated to 882 this evening and was also having issuesā¦
Looking to the connections, Iām seeing attempts to connect to ports like 30000 and 30002.
These are the rules that I have currently active.
roon_ep is the alias for my roon endpoints and trustedsubnets are the euh wellā¦ trusted subnets in my network
If you donāt use vlanās and donāt have fixed ipās for your endpoints and/or remotes, you can ignore these and just allow all ipās from within your network
It might not be necessary to have the 32768:65535 udp and 8008:8009 tcp ports open, but itās saturday 23.00 here and now that itās sort of working, Iād rather spend my time listening to music and drinking than figuring out this mess
I also have this issue on Ubuntu. However, I must be ,missing something, because I canāt connect the Windows or Android app without disabling the firewall.
For Linux based Core server, if youāre running something like UFW firewall, you may need to open the ports. Something like: sudo ufw allow 9330:9339/tcp