Cannot Connect to Server

Support
1

Cannot connect to latest server
I can no longer connect to roon core on my Linux OpenSuse LEAP 15.3 server. It seems to be running:

jarfx:~ # netstat -tulpn | grep Roon
tcp        0      0 0.0.0.0:9332            0.0.0.0:*               LISTEN      2622/RoonAppliance
tcp        0      0 0.0.0.0:9150            0.0.0.0:*               LISTEN      2622/RoonAppliance
tcp        0      0 127.0.0.1:32871         0.0.0.0:*               LISTEN      2234/RoonServer
tcp        0      0 0.0.0.0:30000           0.0.0.0:*               LISTEN      2622/RoonAppliance
tcp        0      0 0.0.0.0:9330            0.0.0.0:*               LISTEN      2622/RoonAppliance
tcp        0      0 100.82.122.97:37939     0.0.0.0:*               LISTEN      2622/RoonAppliance
tcp        0      0 0.0.0.0:9331            0.0.0.0:*               LISTEN      2622/RoonAppliance
udp        0      0 0.0.0.0:42834           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:43035           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:59975           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 100.82.122.97:43791     0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:45454           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:46116           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:46776           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:48985           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:49413           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:50014           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 239.255.255.250:1900    0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:36739           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:37100           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:38332           0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:9001            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:9001            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:9001            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           2622/RoonAppliance
udp        0      0 0.0.0.0:42340           0.0.0.0:*                           2622/RoonAppliance

jarfx:/var/roon/RAATServer/Logs # netstat -tulpn | grep RAATServer
tcp        0      0 127.0.0.1:9004          0.0.0.0:*               LISTEN      10913/RAATServer
tcp        0      0 0.0.0.0:9200            0.0.0.0:*               LISTEN      10913/RAATServer
udp        0      0 0.0.0.0:42925           0.0.0.0:*                           10913/RAATServer
udp        0      0 0.0.0.0:60494           0.0.0.0:*                           10913/RAATServer
udp        0      0 0.0.0.0:33826           0.0.0.0:*                           10913/RAATServer
udp        0      0 0.0.0.0:55776           0.0.0.0:*                           10913/RAATServer
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           10913/RAATServer
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           10913/RAATServer
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           10913/RAATServer
udp        0      0 0.0.0.0:9003            0.0.0.0:*                           10913/RAATServer

I have the firewall off, but it would be nice to know which of these ports are needed to connect.

It was working until I updated my NVidia drivers today and had to reboot. Rebooting does not help, nor does restarting the server;

jarfx:~ # systemctl status roonserver
â—Ź roonserver.service - RoonServer
     Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2022-01-05 11:53:56 EST; 7s ago
   Main PID: 10093 (start.sh)
      Tasks: 163 (limit: 4915)
     CGroup: /system.slice/roonserver.service
             ├─10093 /bin/bash /opt/RoonServer/start.sh
             ├─10099 /opt/RoonServer/RoonDotnet/RoonServer RoonServer.dll
             ├─10132 /opt/RoonServer/RoonDotnet/RoonAppliance RoonAppliance.dll -watchdogport=42673
             ├─10136 /opt/RoonServer/Server/processreaper 10132
             └─10185 /opt/RoonServer/RoonDotnet/RAATServer RAATServer.dll

Jan 05 11:53:56 jarfx systemd[1]: Started RoonServer.
Jan 05 11:53:56 jarfx start.sh[10099]: 00:00:00.000 Warn:  get lock file path: /tmp/.rnsgem0-
Jan 05 11:53:56 jarfx start.sh[10099]: Initializing
Jan 05 11:53:56 jarfx start.sh[10099]: Started
Jan 05 11:53:57 jarfx start.sh[10132]: has mp3float: 1, aac_fixed: 0
Jan 05 11:54:01 jarfx start.sh[10099]: Running
jarfx:~ #

After this restart, my android app saw the core, but could not connect.

RoonServer log:

01/05 11:57:46 Info: [importstatus] notifying 0 imports completed
01/05 11:57:50 Trace: [music/searchindex]  removed: 0 albums, 0 tracks, 0 works, 0 performers, 0 labels, 0 genres
01/05 11:57:50 Trace: [music/searchindex]  added: 11927 albums, 160320 tracks, 51818 works, 39141 performers, 833 labels, 1261 genres
01/05 11:57:56 Trace: [raatserver] [System Output] client connection failed. Retrying in 750ms
01/05 11:57:56 Trace: [raatserver] [Built-in Digital Output] client connection failed. Retrying in 750ms
01/05 11:57:57 Info: [raatserver] [Built-in Digital Output] connecting (attempt 3)
01/05 11:57:57 Info: [raatserver] [System Output] connecting (attempt 3)
01/05 11:58:00 Info: [stats] 27399mb Virtual, 5132mb Physical, 3157mb Managed, 286 Handles, 99 Threads
01/05 11:58:05 Debug: [easyhttp] [17] POST to https://discovery.roonlabs.net/1/query returned after 241 ms, status code: 200
01/05 11:58:07 Trace: [raatserver] [System Output] client connection failed. Retrying in 1125ms
01/05 11:58:07 Trace: [raatserver] [Built-in Digital Output] client connection failed. Retrying in 1125ms
01/05 11:58:08 Info: [raatserver] [Built-in Digital Output] connecting (attempt 4)
01/05 11:58:08 Info: [raatserver] [System Output] connecting (attempt 4)
01/05 11:58:15 Info: [stats] 27262mb Virtual, 5128mb Physical, 3158mb Managed, 286 Handles, 83 Threads
01/05 11:58:18 Trace: [raatserver] [System Output] client connection failed. Retrying in 1687ms
01/05 11:58:18 Trace: [raatserver] [Built-in Digital Output] client connection failed. Retrying in 1687ms
01/05 11:58:19 Info: [raatserver] [System Output] connecting (attempt 5)
01/05 11:58:19 Info: [raatserver] [Built-in Digital Output] connecting (attempt 5)

RAATServer Log:

01/05 11:56:29 Info: Starting RAATServer v1.8 (build 884) stable on linuxx64
01/05 11:56:29 Trace: [RAATServer] detected ALSA support
01/05 11:56:29 Warn: [bits] myinfo: {
    "os": "Linux 5.3.18-59.37-preempt",
    "platform": "linuxx64",
    "machineversion": 100800884,
    "branch": "stable",
    "appmodifier": "",
    "appname": "RAATServer"
}
01/05 11:56:30 Debug: [easyhttp] [1] POST to https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery. returned after 295 ms, status code: 200
01/05 11:56:30 Trace: [bits] updated bits, in 338ms
01/05 11:56:30 Info: [RAATServer] creating RAAT__manager
01/05 11:56:30 Info: [RAATServer]     appdata_dir  = /var/roon/RAATServer
01/05 11:56:30 Info: [RAATServer]     unique_id    = 066639cc-3251-43b9-95ae-b282e08bb6f2
01/05 11:56:30 Info: [RAATServer]     machine_id   = 22778568-33cc-fb3d-7232-92565a529f88
01/05 11:56:30 Info: [RAATServer]     machine_name = jarfx
01/05 11:56:30 Info: [RAATServer]     os_version   = Linux 5.3.18-59.37-preempt
01/05 11:56:30 Info: [RAATServer]     vendor       =
01/05 11:56:30 Info: [RAATServer]     model        =
01/05 11:56:30 Info: [RAATServer]     service_id   = d7634b85-8190-470f-aa51-6cb5538dc1b9
01/05 11:56:30 Info: [RAATServer]     is_dev       = False
01/05 11:56:30 Trace: [raatmanager] starting
01/05 11:56:30 Trace: [raatmanager/linux] FOUND id=hw:CARD=PCH,DEV=0 usb_id=
01/05 11:56:30 Trace: [raatmanager/linux]       vendor=                               name=HDA Intel PCH ALC3234 Analog  
01/05 11:56:30 Trace: [raatmanager] [HDA Intel PCH ALC3234 Analog] loaded config from /var/roon/RAATServer/Settings/device_75bb55b2e6d1f2d4cd04d3605fd16d7e.json
01/05 11:56:30 Trace: [raatmanager] initialized
01/05 11:56:30 Info: [RAATServer] running RAAT__manager
01/05 11:56:30 Trace: [raatmanager] starting discovery
01/05 11:56:30 Trace: [discovery] starting
01/05 11:56:30 Info: [discovery] [iface:lo:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
01/05 11:56:30 Info: [discovery] [iface:lo:127.0.0.1] multicast send socket is bound to 0.0.0.0:33826
01/05 11:56:30 Info: [discovery] [iface:eth0:192.168.1.5] multicast recv socket is bound to 0.0.0.0:9003
01/05 11:56:30 Info: [discovery] [iface:eth0:192.168.1.5] multicast send socket is bound to 0.0.0.0:42925
01/05 11:56:30 Info: [discovery] [iface:tailscale0:100.82.122.97] multicast recv socket is bound to 0.0.0.0:9003
01/05 11:56:30 Info: [discovery] [iface:tailscale0:100.82.122.97] multicast send socket is bound to 0.0.0.0:55776
01/05 11:56:30 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
01/05 11:56:30 Trace: [raatmanager] starting server
01/05 11:56:30 Info: [jsonserver] listening on port 9200
01/05 11:56:30 Trace: [raatmanager] announcing
01/05 11:56:30 Debug: [discovery] broadcast op is complete
01/05 11:56:30 Trace: [inetdiscovery] added device raatserver/066639cc-3251-43b9-95ae-b282e08bb6f2 in addr:__ADDR__
01/05 11:56:30 Trace: [inetdiscovery] added service com.roonlabs.raatserver.tcp for device raatserver/066639cc-3251-43b9-95ae-b282e08bb6f2
01/05 11:56:35 Trace: [ipaddresses] enumerating addresses
01/05 11:56:35 Trace: [ipaddresses]    FOUND   lo 127.0.0.1
01/05 11:56:35 Trace: [ipaddresses]    FOUND   eth0 192.168.1.5
01/05 11:56:35 Trace: [ipaddresses]    FOUND   tailscale0 100.82.122.97
01/05 11:56:36 Debug: [easyhttp] [2] POST to https://discovery.roonlabs.net/1/register returned after 186 ms, status code: 200
01/05 11:56:36 Trace: [inetdiscovery] registered 1 devices, 1 services
01/05 11:56:40 Trace: [RAATServer] refreshing @ 10s
01/05 11:56:40 Trace: [raatmanager] announcing
01/05 11:56:40 Debug: [discovery] broadcast op is complete
01/05 11:57:35 Trace: [jsonserver] [127.0.0.1:40494] accepted connection
01/05 11:57:35 Trace: [jsonserver] [127.0.0.1:40494] GOT[LL] [1] {"request":"enumerate_devices","subscription_id":"0"}
01/05 11:57:35 Trace: [jsonserver] [127.0.0.1:40494] SENT [1] [nonfinal] {"status": "Success", "devices": [{"device_id": "hw:CARD=PCH,DEV=0", "type": "alsa", "name": "HDA Intel PCH ALC3234 Analog", "config": {"output": {"type": "alsa", "device": "hw:CARD=PCH,DEV=0", "name": "H
01/05 11:57:35 Trace: [jsonserver] [127.0.0.1:40494] GOT[LL] [2] {"request":"enable_device","device_id":"hw:CARD=PCH,DEV=0","subscription_id":"1"}
01/05 11:57:35 Trace: [raat_wrap] creating new RAAT device
01/05 11:57:35 Trace: [RAAT::HDA Intel PCH ALC3234 Analog] [info] initializing info dictionary
01/05 11:57:35 Trace: [RAAT::HDA Intel PCH ALC3234 Analog] [info] inserting raat_version -> 1.1.38
01/05 11:57:35 Trace: [RAAT::HDA Intel PCH ALC3234 Analog] [info] inserting protocol_version -> 3
01/05 11:57:35 Error: [raat_wrap] RAAT__OUTPUT_PLUGIN_STATUS_DEVICE_OPEN_FAILED failed: failed to initialize alsa output
01/05 11:57:35 Trace: [jsonserver] [127.0.0.1:40494] SENT [1] [nonfinal] {"device": {"device_id": "hw:CARD=PCH,DEV=0", "type": "alsa", "config": {"output": {"type": "alsa", "device": "hw:CARD=PCH,DEV=0", "name": "HDA Intel PCH ALC3234 Analog", "dsd_mode": "none"}, "unique_id":
01/05 11:57:35 Trace: [jsonserver] [127.0.0.1:40494] SENT [2] [nonfinal] {"status": "DeviceInitFailed"}

What do I do?

2

I’ve moved your post from an old feedback thread to a fresh post in the Support category of the forum. Here it will be seen by the Support team.

In order for Roon’s @support team to better assist you, please provide a brief description of your current setup and the nature of the issue using this link as a guide.

Make sure to describe your network configuration/topology, including any networking hardware currently in use, so they have a clear understanding of how your devices are connected.

4

You appear to have a VPN? in place:
FOUND tailscale0 100.82.122.97

I would shut it down to limit possible issues.
Looking again at your post, Roon appears to be listening to lo0 @127.X and to 100.82.

Your 192.168.1.5 is missing entirely.

5

I only installed tailscale because a post here said that it was needed to access roon from outside my router. But it is removed now and I still cannot connect.

My server is ON 192.168.1.5.
For sshd, the port list is

netstat -tulpn | grep sshd

tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2293/sshd: /usr/sbi
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 5546/sshd: jar@pts/
tcp6 0 0 :::22 :::* LISTEN 2293/sshd: /usr/sbi
tcp6 0 0 ::1:6010 :::* LISTEN 5546/sshd: jar@pts/
and sshd works

It all was working until I rebooted the server today. I changed only the non-roon software updates for NVidia.

My Roon clients are
Mac App - ethernet
Android and iPad apps - on WiFi.
None of them connect.
I have a very complicated network with about 30 devices, a cable modem in bridge mode, a router, a separate Linksys WiFi mesh, multiple switches.
But the problem is with this new build. I have had it since in beta.

Roon support said they turned on diagnostics for my server. Where do I look to see them?

6

I would check to see if roon is listening at the 192. address.
I hope @support can help you, I don’t know about diagnostic mode at all.

FWIW, your setup sounds very similar to mine.

7

That would be for Roon HQ to be able to view, not available to the user…to my knowledge.

1 Like
8

It must be since the logs list the unsuccessful connections.

9

Your first post contained:
netstat -tulpn | grep Roon
I do not note 192.168.1.5 in there at all.
You have since killed the VPN, did you restart roonserver and would you check what it is listening on again, please?

10

Restarted, no luck

jarfx:/var/roon # systemctl restart roonserver
jarfx:/var/roon # netstat -tulpn | grep RoonServer
tcp 0 0 127.0.0.1:39523 0.0.0.0:* LISTEN 16312/RoonServer
jarfx:/var/roon # netstat -tulpn | grep RoonAppliance
tcp 0 0 0.0.0.0:9332 0.0.0.0:* LISTEN 16345/RoonAppliance
tcp 0 0 0.0.0.0:9150 0.0.0.0:* LISTEN 16345/RoonAppliance
tcp 0 0 192.168.1.5:42919 0.0.0.0:* LISTEN 16345/RoonAppliance
tcp 0 0 0.0.0.0:30000 0.0.0.0:* LISTEN 16345/RoonAppliance
tcp 0 0 0.0.0.0:9330 0.0.0.0:* LISTEN 16345/RoonAppliance
tcp 0 0 0.0.0.0:9331 0.0.0.0:* LISTEN 16345/RoonAppliance
udp 0 0 0.0.0.0:45454 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:45545 0.0.0.0:* 16345/RoonAppliance
udp 0 0 192.168.1.5:49411 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:33193 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:34488 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:1900 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:1900 0.0.0.0:* 16345/RoonAppliance
udp 0 0 239.255.255.250:1900 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:36088 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:5353 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:5353 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:38253 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:38904 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:56553 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:41263 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:9001 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:9001 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:9003 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:9003 0.0.0.0:* 16345/RoonAppliance
udp 0 0 0.0.0.0:9003 0.0.0.0:* 16345/RoonAppliance
jarfx:/var/roon # netstat -tulpn | grep RAATServer
tcp 0 0 127.0.0.1:9004 0.0.0.0:* LISTEN 16399/RAATServer
tcp 0 0 0.0.0.0:9200 0.0.0.0:* LISTEN 16399/RAATServer
udp 0 0 0.0.0.0:48951 0.0.0.0:* 16399/RAATServer
udp 0 0 0.0.0.0:34529 0.0.0.0:* 16399/RAATServer
udp 0 0 0.0.0.0:40384 0.0.0.0:* 16399/RAATServer
udp 0 0 0.0.0.0:9003 0.0.0.0:* 16399/RAATServer
udp 0 0 0.0.0.0:9003 0.0.0.0:* 16399/RAATServer
udp 0 0 0.0.0.0:9003 0.0.0.0:* 16399/RAATServer

11

well now at least it is listening. RAAT does not appear to be though.
restart that . . .
if nothing else, you’ll be in a solid state when support can help out.
Hopefully.
I have no idea how the client and server communicate here so, apologies.

12

The RAATServer is not listed in my services list – only RoonServer is. The latter shell script must start both?

13

I wish I could help further. But that would be my guess.
man roonserver would be lovely about now.
$ man roonserver
No manual entry for roonserver
16

14

You did get me to remove the VPN. Thanks for trying.

1 Like
15

Welcome, thank you for trying.
It will make their life, and thus yours, easier.

17

Hi @James_Rome ,

Are you still seeing this issue at the present time? In your email correspondence, you indicated that the sever has finally connected, has it been stable since then? Let us know!

19

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