Connection Issue Indicated by Status Code 200 in RAAT Server Logs (ref#ESANC6)

Support
1

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Waiting for your Roon Server"

What happens if you press the "Select a different Roon Server" button?

· I don't see Roon Server.

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *Ethernet*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· Roon on a *NAS* (Synology, QNAP, ASUSTOR)

Select any of the following components that are present in your local network setup

· None of the above

Describe the issue

L.S. I have read the RAAT Server logs. And here there is a status code: 200 which seems to be part of the problem. This has been going on for three weeks. I don´t want to reïnstall Roon, because I think it is not a Roon-Server problem, but some kind of (other) connection issue. I hope You can somehow enlighten me. Thanks in advance for Your help. With kind regards John Eberson

Describe your network setup

I don't think there is a problem with my network setup: I have three servers, two nasses (on backup), all connected through a 1GB router (12 connections) with an internetconnection through a Fritzbox 7590 modem connection to a fiberglas network (WAN). Which has been and still is working without any problems. The connection failure started after updating the Roon server. It seems unl;ikely this is a coincidence. I now us Tidal to play my music, but I am missing the convenience of the Roon solution.

2

Please see:

There is no problem with that: HTTP - Wikipedia

3

Hi @John_Eberson,

Thank you for your post.

We’ll first need to migrate your RoonServer to a docker/container, since the minimum requirements have changed slightly with the release of the latest Roon build.

Here’s a guide for how to set up docker on your QNAP:

https://help.roonlabs.com/portal/en/kb/articles/installing-roonserver-on-qnap-with-docker#

Generally speaking, you’ll be restoring a Backup to “migrate” your database to the new setup. Make sure you disconnect/remove your Watched Folders in Roon Settings → Storage first to prevent inadvertently erasing your Play History when the new server scans the location.

You mentioned that you’ve been encountering connectivity problems with Roon for the last three weeks. The 200 status code indicates a successful connection, so it’s usually easier to start from the timestamp of the symptom you are experiencing. What do you see in Roon when you have connectivity problems? Is playback breaking/interrupting to a Zone?

We’re here if you have any questions about migrating to the docker. We’ll watch for your reply in the meantime. Thank you!