Roon Remote on iOS Does Not See Core Over Tailscale

I’ve found browsing in Arc to be extremely lacking so I would like to use Roon Remote instead. However, contrary to what some others have said about Tailscale just working, I have not been able to get it to do so. I have it running on my Core and installed and running on my iPhone but Roon Remote never finds the Core over WiFi in a remote location. I can tap the help and enter the Tailscale IP of the Core and click scan but nothing happens. I can get pings in a ping utility just fine on the iPhone using the Tailscale IP of the Core but that’s it. Beyond that, the Core seems not to exist as far the Roon Remote is concerned.

Has anyone seen this and found a way to get it to actually do something?

I decided to try on my Windows 10 laptop and it at least sort of works, but I am unable to see any of my audio devices to actually play anything locally. Turning off the Windows firewall does nothing, so still stuck.

Okay, I got it to work on the iPhone but only on cellular. Something seems to be blocked over WiFi which is weird because this is the reverse of what some other posts have suggested. I really need it to work over WiFi. What I haven’t tried is Ethernet, which may work but I don’t have a device with me that has it available.

My intention is to set this up on a Raspberry Pi running Tailscale and routing to something like an Eversolo DMP-A6 in a remote setting about 400 miles from the server. I don’t believe there is a way to install Tailscale on the A6 directly but I don’t have one so I can’t test it out. I’m just doing site testing now with what I have.

I’ve since gotten it to work on both Windows and iPhone, via a combination of WiFi, cellular and an Ethernet adapter I found, but none of it works consistently or dependably. Very odd and not at all like the “it just works” billing. Frustrating!

I figured how to get this to work . Had to advertise a subnet route on my Core running Ubuntu and then go to the admin page and approve it.

sudo tailscale up --advertise-routes=192.168.1.0/24

I also had to enable the exit node on the Core. After that, I could add the IP of the Core through the Help manual IP interface and access it with the iPhone’s audio hardware. The Exit node being on prevents other network activity at least how I have it, but it only needs to be enabled long enough to perform discovery. Since this has to be done as a second step besides just enabling Tailscale, it’s a bit of a pain.

2 Likes