Roon Remote can't connect to Core right after update to v1.8 build 880

Roon Core Machine

Linux PC, Ubuntu 16.04 LTS, Kernel 4.13.0, Intel CoreDuo2, 8 GB

Networking Gear & Setup Details

Wired Gigabit ETH & WiFi UniFi AP

Connected Audio Devices

  • Roon Bridge running on RasberryPi (v1.8 build 880) [M2Tech USB Audio 2.0]
  • Roon Bridge running on BBB (v1.8 build 880) [offline whil log was generated]

Number of Tracks in Library

22000 tracks

Description of Issue

The system was running OK. Then today the update to 880 was announced. I’ve updated the core and all bridges and the remote I was using.
Right after the update the remote could no more connect to the core.

Tried different remotes, none does connect anymore.
Reinstalled the core, disabled IPv6 on core server as suggested in another post.
No effect.

Checked the log, but it gives me no real hint where the problem is. There are some entries stating “Connection refused”, but a double check with older log showed that these entries already existed when everything was working fine.

If you need I can provide the core logs.

Can you please help to find a solution? Thanks a lot!

Daniel

Similar problem with my setup. I have ROCK installed on a NUC I5 gen. 7, worked well until a upgraded to v1.8 build 880. The remotes (android and Windows PC) can’t connect to the core. The windows network diagnosis shows that the NUC is on the network, but are not able to connect to it.
I will be wery happy if I could get some help with this

1 Like

I had the same problem, IOS devices not connecting & not visible in “settings/audio” so I rebooted the IOS devices and they started working again, it might be worth a try.

1 Like

Check out, might be the same issue: Connection failed and Chromecast issues: Roon using new/additional network ports since 880
Roon changed the network ports on 880

1 Like

Hey @Daniel_Hoberg,

Welcome to the community and, sorry the latest update didn’t go as smoothly as we’d hoped.

Would you please be able to share what devices did you try using as Roon Remotes to connect to your Core?

1 Like

Aaaah! Thanks a million! Adding the new the firewall ports solved it!
For some reason I did not check/think of the firewall…

Hi Rebeka,

thanks for getting back to my post. @Christophe_Saelens already pointed out the right answer - the used ports changes since the build 880.

Please do include such changes in the release notes for future updates! There are people out there using a customised firewalls… :wink:

Regards, Daniel

See the reply of @Christophe_Saelens - for me it was the solution!

I’ve opened the proposed ports, and connected to the core again. But when I connected some hours later, same problem. If I turn the NUC off and start it again, I can connect to it, but only once. Very happy for suggestions, they have helped me some of the road!

I have the same issue. My remote is a Beaglebone Black with Debian 10 and in the logs it is possible to see:

Dec 19 12:48:45 beaglebone start.sh[205]: #033[0;37;1m#033[0;0m00:21:46.004 #033[0;31mWarn: exception starting raatserver: System.Net.Sockets.SocketException (0x80004005): Connection refused
Dec 19 12:48:45 beaglebone start.sh[205]: at System.Net.Sockets.TcpClient…ctor (System.String hostname, System.Int32 port) [0x0006d] in :0
Dec 19 12:48:45 beaglebone start.sh[205]: at Sooloos.RAATServer.ConnectOrStartAndWaitForExit (System.String path, System.String args, System.Action1[T] status, Base.ChildProcess& p) [0x00165] in <f2522c4212004c68a62247d3366268e4>:0 #033[0;0m Dec 19 12:48:45 beaglebone start.sh[205]: Not Running (.o) Dec 19 12:48:47 beaglebone start.sh[205]: #033[0;37;1m#033[0;0m00:21:48.025 #033[0;37;1mInfo: ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer#033[0;0m Dec 19 12:48:47 beaglebone start.sh[205]: Running Dec 19 12:48:53 beaglebone start.sh[205]: #033[0;37;1m#033[0;0m00:21:54.050 #033[0;31mWarn: exception starting raatserver: System.Net.Sockets.SocketException (0x80004005): Connection refused Dec 19 12:48:53 beaglebone start.sh[205]: at System.Net.Sockets.TcpClient..ctor (System.String hostname, System.Int32 port) [0x0006d] in <ef2b8cc0336c473382f0e9112dd3c795>:0 Dec 19 12:48:53 beaglebone start.sh[205]: at Sooloos.RAATServer.ConnectOrStartAndWaitForExit (System.String path, System.String args, System.Action1[T] status, Base.ChildProcess& p) [0x00165] in :0 #033[0;0m
Dec 19 12:48:53 beaglebone start.sh[205]: Not Running (.o)
Dec 19 12:48:55 beaglebone start.sh[205]: #033[0;37;1m#033[0;0m00:21:56.066 #033[0;37;1mInfo: ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer#033[0;0m
Dec 19 12:48:55 beaglebone start.sh[205]: Running

but I am not sure if this hints to anything.

My core is macOS Big Sur 11.6.1 with Core v1.8(Buid 882)

In Settings and About I can see my Beaglebone Black listed but cannot select it in Audio Zones.

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