Roon ARC connection issues on Ubuntu sever with Tailscale (ref#SX2SDH)

What’s happening?

· Other

Describe the issue

Hello,
I have followed the instructions and set up Tailscale on my Roon core Ubuntu server. I can ping back and forth from my phone to the Roon Core over Tailscale using cell service. But when I try to connect to Roon Arc it just spins. It goes to "Roon Server Last seen less than a minute ago" to "Only available on your network" but never actually connects.

I have the port set to zero and it shows "not ready"

I cannot connect using Roon ARC inside my network either. My phone is on the same subnet and I can ping its local IP.

There is no firewall on the rooncore server.


Can I get some help on this please?

Describe your network setup

Unifi networking with various stwitches and access points. Unifi UXG-Pro Gateway. AT&T 1 GB Synchronous fiber.

I believe this is wrong. Port 0 is used to disable Roon ARC support in the server. Unless, it is already in use, Roon ARC should be set to the default port (55000).

Port numbers less than 1024 should not be used.

The ‘not ready’ status indicator in the Roon → Settings → Roon ARC page refers strictly to the port forwarding setup on the router. This is not necessary when using Tailscale and so the ‘not ready’ status indication is irrelevant.

However, the ARC port is used for both local network access (which is what Tailscale gives you) and remote access via port forwarding.

I’ll give it another try with the default port. thanks.

I set port back to default and Same issue. It cycles between “Not accessible from outside your network” to “Rooncore” spinning every second. Eventually, it will say cannot connect to your Roon Server in a red bar on the ARC app.

I can ping the Roon Server over tailscale from my iPhone on cellular so I know the route is there and working.

When I get back on my WiFi and turn off Tailscale I am unable to connect using Roon Arc, but that may be normal, I am unsure about that. But it displayed the same behavior on the Arc app on my phone (spinning between the above messages)

This is not normal. This needs to be fixed first before anything else.

Tailscale makes it look (to the Roon Server software) as if you are connecting from your local network. Thus, If your local network does not work, Tailscale will not work either.

Can you check the ip addresses of your Roon Server and your phone (if possible - it should be visible on your router Web UI is it is not visible any other way) and check that they are both in the same subnet (ie, assuming a usual netmask of 255.255.255.0, the first three numbers of the 4 number ip address should be the same).

They are in the same subnet.

I seem to remember reading of some people that had issues at one point with iPhones when they were set to generate a ‘private’ mac address. I don’t know what the setting was and I don’t know if it is still a problem but, if you are using an iPhone, then, perhaps you should try turning that off.

Android devices, (at least my Pixel 6 on Android 15) now have a similar setting in the WiFi settings for each remembered WiFi network. In the WiFi network ‘Privacy’ settings, you can choose between ‘Use randomised MAC’ or ‘Use device MAC’. If you are using the former, it might be worth trying the ‘Use device MAC’ setting.

If this does not solve your issue, then, assuming your WiFi is reliable and achieves half decent data rates, then I am unable to think of anything else.

Yeah, my network is in good shape (I’m a 30-year IT pro, though that does not eliminate mistakes…). I have good throughput and low latency across all areas of the network.

I believe that is called Private WiFi Address in iOS. I turned it off and still the same behaviour.

I believe it is seeing the server because it has this message “Roon Server last seen less than a minute ago”. It’s just not able to connect.

Thank you for your help. It is a mystery so far.

1 Like

FYI: This in the Linux instructions says to try putting 0 in the port

  1. Restart RoonServer and ARC on your Linux machine and your phone.

" 1. Turn off WIFi, leaving only the cellular data connection. Open the settings page in ARC and look for “Connected” to see if ARC is working.

  1. If not connected, go into Roon and disable port forwarding. Go to → Settings → Roon ARC and enter “0” in the box for “Port”. If successfully disabled, you should see “Not Ready”’

Hi @Robert_Donovan,

Thank you for your post. RoonServer diagnostics indicate that the Tailscale IPv4 address isn’t available to to Roon. We want to check for a conflict with the Tailscale address range.

Two quick tests for due diligence:

First, in the Tailscale Admin console, verify that “Disable IPv4” is toggled off.

Next, use the Tailscale Status command to verify whether Tailscale has an active IPv4 address on this Ubuntu machine.

Please let us know the results.

It has an IPv4 address that I can ping from my phone on cellular when connected to Tailscale on the phone. I can also ping it from other machines on my Tailscale network. Tailscale is also configured on the Roon Core installation to allow local LAN access.

In the Tailscale Admin it shows the IPv4 address.

And yes tailscale status shows the rooncore server’s Tailscale IPv4 address

@connor anything more?

Hello @Robert_Donovan ,

I am reviewing your post and I noticed you mentioned this aspect:

If ARC is not working even on local WiFi without Tailscale being involved at all, then it sounds like there is a deeper issue than just Tailscale, and something is preventing communication between the Server and the ARC device.

Since you have a Linux Server machine, I would check to see how the behavior is like if you try to temporarily host the Roon Server on another machine (Windows/Mac), or double check the firewall configuration on the PC. I know you mentioned it was off, but it sounds like something is still blocking the connection. If you confirm the issue only occurs on the Linux Core, then the following articles might help:

Thanks @noristake I’ll take a look again. I have confirmed that ufw is disabled but perhaps there is something else on that server causing issues. Thanks for the two posts. I will let you know what I find.

Sounds good @Robert_Donovan - let us know your findings!

Our team will be OOO until Monday, December 2nd - hope you’re able to enjoy the holiday period until then if you’re stateside! :raised_hands:

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