Unable to log in on Windows PC and Android devices (ref#MB059V)

[jose_manuel_gallardo]

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

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

What kind of device are you using to perform the login?

· Android

Where are you trying to login?

· I can't log into Roon

Please try to restart your Roon Server by closing the Roon Server app in the taskbar (MacOS), task manager (Windows) or rebooting your Roon Server machine.

· No, the issue remains the same

Different device

· I cannot switch to a different device

Are you still facing the issue on the different device

· No, the issue remains the same

Record the timestamp

· Cannot find my roon server, reboot and try with different devices and problem still

Describe the issue

Cannot log in on my windows pc neither on my Android devices

Describe your network setup

Router is a live box fibra tried inserted IP manually but keeps searching for roon

[alex_h (Alex)]

Hello @jose_manuel_gallardo,

Thank you for reaching out to us.

Could you please follow the instructions found hereand upload a set of logs to our File Uploader?

Also, could you please let us know where you are running the updated version of Roon? Is it running in a container, or as a standalone app?

Once the logs have been uploaded, please let us know so we can check the server for your files.

Thanks!

[connor]

Hi @jose_manuel_gallardo,

We’ve not seen any diagnostic log uploads to our server (see link in the post above). Our team is eager to investigate logs and help pinpoint this problem.

We do, however, see some recent account activity associated with your Roon account. Are you still experiencing issues with this remote?

[jose_manuel_gallardo]

Hi, Connor

As I did not receive any more replies from your side, on different posts
about Roon access problems with Qnap NAS, I did follow the instructions on
how to create a container in the container station with a link from Roon on
how to do it.
I tried several times as was little bit difficult for me but finally got
access the only problem is on how my music is now on folders, as I have on
my NAS music in two different HDD discs VOL1 +VOL2
On the link to create container there is option for music file and to add
additional mount.  Now I have  no ideal folders to manage.

I attached some screencaptures here to show it to you.

Previously I have
 in Vol1
POP-Rock
Blues
in Vol2
Jazz
Folk
Country
Classic


 If any can be done to solve it, please advise.

Best regards
Jose

[benjamin]

Hey @jose_manuel_gallardo,

Thanks for the update! When you set up Roon in QNAP Container Station using Roon’s Docker instructions, the music folders from your NAS volumes (Vol1 with POP-Rock/Blues and Vol2 with Jazz/Folk/Country/Classic) need to be explicitly bind-mounted into the container.

Right now they aren’t, the paths the container is looking for (/Music and /share/container/roon-backups/JAZZ) either don’t exist or aren’t properly mapped.

Here are some next troubleshooting steps:

1. Fix the container volume mounts in QNAP Container Station

You need to edit your Roon container and add bind mounts for each music folder. In Container Station:

• Go to your Roon container → Edit → Storage/Volumes
• Add a mount for each music location, for example:
  • Host path: /share/VOL1/POP-Rock → Container path: /music/pop-rock
  • Host path: /share/VOL1/Blues → Container path: /music/blues
  • Host path: /share/VOL2/Jazz → Container path: /music/jazz
  • (and so on for Folk, Country, Classic)

The exact host paths on your QNAP will look something like /share/CACHEDEV1_DATA/Music or /share/VOL1_DATA/... — check your QNAP File Station to confirm the exact paths.

2. Update Roon’s watched folders to match the new container paths

After fixing the mounts, go into Roon → Settings → Storage and point each watched folder to the new container-internal paths (e.g. /music/jazz, /music/pop-rock, etc.).

3. The /share/container/roon-backups/JAZZ path looks wrong

That path looks like it was set up as a workaround and is mixing backup storage with music storage. Once you have proper music mounts, remove this location from Roon’s storage settings.

Let me know if this helps!

[jose_manuel_gallardo]

Benjamin, thanks for yours but I am still doing something wrong.

I create volumes as I didnt before, deleted container application and creating new one with new instructions, incorporating mounts additionals.

When running ROON tried to create folders accordingly all ok except for one folder POPROCK unable to do it.

I attached screencaptures for your info and please can you tell me what is wrong

[jose_manuel_gallardo]

Benjamin, I solved it, delee vol in container for folder and edit new again, then add in roon and worked. Guess was I did name it when create volume without blank space POPROCK instead of POP ROCK. Now it works.

I checked for backups and in file station each folder has a roon backupfolder.

Only question is why sometimes when start running roon do not detect audio zone (my amplifier connected via usb to my NAS) only happens sometimes I have restart NAS, Roon, etc to detect my audio zone

Apart from that I think now all is ok.

thanks and regards

[noris]

Hey @jose_manuel_gallardo,

Glad to hear everything is better. As for the audio zone not being detected, can you please let us know the exact local time and date when it happens next? We’ll enable diagnostics to see if logs contain any clues.

[jose_manuel_gallardo]

Thanks for yours, Noris

Tried to connect yesterday about 11 am Madrid (Spain) time.

I switch off NAS and roon, restart and connect again then detected audio zone, this is not the first time happens.

Apart from the big problem with my Qnap NAS that Roon went off, now solved with container app.

But usual problems are audio zone not detected or Ronn server not detected.

Only solution I have found is swithch off NAS and restart again which is sometimes frustrating

I have no clue as my devices are properly connected to router and my NAS via usb to my amp.

Thanks for all support

Best regards/Jose

[benjamin]

Hi @jose_manuel_gallardo,

Thanks for sharing the above timestamp! From a fresh Roon Server diagnostic report, we can see the USB DAC disconnecting right after playback was paused — OnDisconnected → Connection refused → DeviceRemoved. This is may be a USB device enumeration problem, not a Roon problem. When the amp is idle and Roon releases the audio device (which it does after 5 seconds of pause), Linux drops the USB connection.

As a next step, can you try disabling USB auto-suspend in the Roon QNAP container/system. On Linux you can do this by adding to the container startup:

echo -1 > /sys/module/usbcore/parameters/autosuspend

Or in /etc/rc.local / the container’s init scripts. Alternatively, in the QNAP power settings, disable USB power management/selective suspend if that option exists in your QNAP firmware.

I would also see about trying to give the KSTB6130 a static IP in your router’s DHCP settings, and make sure multicast is enabled on your network switch/router.

Let me know if the above help!

[jose_manuel_gallardo]

Hi, Benjamin

This is not easy for me, as I do not quite understand how to do it.

I tried to find on my Qnap NAS disabling USB auto suspend and cannot find it.

Alsoon container I do not know where I have to insert line
echo -1 > /sys/module/usbcore/parameters/autosuspend

KSTB6130 is my router what I did is give static IP to my NAS on router settings.

If you can help me on this, when start roon this morning happen same again, I did restart NAS and roon, audio usb to my amp show on again

I attached screenshot of my container, shall I add instruction after line 19 or how to proceed

Please advise

best regards

[vadim]

Hello @jose_manuel_gallardo,

You are doing great! Please don’t worry—handling terminal commands can feel intimidating, but you are looking in exactly the right place.

You are completely right to be cautious about editing that container file. As it turns out, the USB power-saving feature isn’t actually happening inside the Roon container itself—it is being managed by the main host operating system of your QNAP NAS. Because the NAS hardware controls the physical power to its own USB ports, when Roon pauses the music, the QNAP thinks the port is idle and cuts the power connection to your amplifier. When you restart the whole NAS, it wakes the port back up, which explains why it keeps temporarily fixing the problem.

To permanently stop the QNAP from turning off your USB audio port, we need to run that command directly on the NAS system. Here is the easiest way to do it:

Step 1: Enable SSH Access on your QNAP

To send a command directly to the NAS operating system, we need to briefly turn on secure remote access:

1. Log into your QNAP desktop in your web browser.
2. Open the Control Panel and go to Network & File Services > Telnet / SSH.
3. Check the box to Allow SSH connection. (You can leave the port at 22).
4. Click Apply.

Step 2: Run the Command (From a Windows PC or Mac)

• If you are on Windows: Press the Windows Key + R, type cmd and hit Enter to open the Command Prompt.
• If you are on a Mac: Open the Terminal app.

Type the following command to connect to your NAS (replace YOUR_NAS_IP with the actual IP address of your QNAP, like 192.168.1.50) and press Enter:

ssh admin@YOUR_NAS_IP

It will ask for a password—type your main QNAP administrator password and hit Enter (you won’t see the letters appearing as you type, which is normal security behavior).

Once you are successfully logged into the QNAP console, simply copy and paste this exact line and press Enter:

echo -1 > /sys/module/usbcore/parameters/autosuspend

This instantly tells the QNAP’s hardware engine: “Do not ever put the USB controller to sleep.”

Step 3: Turn off SSH

Now that the command is sent, go back to your QNAP browser tab, uncheck the “Allow SSH connection” box, and click Apply to lock down your security again.

Try leaving your amplifier idle for a few hours now without playing music. When you open Roon later, your USB zone should remain perfectly active and ready to play without requiring any more frustrating NAS reboots! Let us know if you hit any snags during the SSH login.

[jose_manuel_gallardo]

Hi, Vadim

I did step 1+2 as mentioned

When enter command: echo -1 > /sys/module/usbcore/parameters/autosuspend and click enter command line dissapear

I repeat the process twice

Did step 3 turn off SSH

But the problem with audio zone still persists

I have to reboot NAS with amplifier on to recover my audio amp.

FYI I have my NAS configured to switch off/on during night also my amp is swiched off when starts running NAS in the morning my amp is switched off and do not detect it when on I have to reboot my NAS keeping my ampon to detect.

[alex_h (Alex)]

Hi @jose_manuel_gallardo,

You did an amazing job running those commands! The terminal disappearing simply means the instruction was accepted successfully.

However, the reason the issue persists is a hardware timing conflict: because your NAS boots up in the morning before the amplifier is turned on, the NAS fails to detect it. Since Roon runs in a Docker container, it can only see hardware that was already active during the NAS boot sequence.

To fix this easily without any more terminal commands, you just need to ensure the amplifier is powered on before the NAS starts up. Alternatively, you can change your QNAP power schedule to boot up 15 minutes after you normally turn on your amp, or simply leave the NAS running 24/7.

Let us know if changing this power order gets your audio zone working right away!

[benjamin]

Hi @jose_manuel_gallardo,

Since a few days have passed, we wanted to quickly check in and see if the above reply from Alex may have helped.

We’ll be monitoring for your reply and results, thank you!

[jose_manuel_gallardo]

Hi Benjamin

Not quite happy with solution as I have to keep on my NAS 24/7 or modify power schedule which is not an easy task, as do not have fix time for listening music, hard to synchonize both I would rather pursuit for a better solution if can find it.

best regards

Jose

[benjamin]

Hi @jose_manuel_gallardo,

Thanks for the reply. I totally understand the frustration, but this is actually by design. Roon Server is built to run 24/7, and that’s really the intended use case. It’s not a limitation so much as the architecture Roon is built around. The server needs to be constantly available so it can index your library, handle metadata updates, and be ready the moment any endpoint (your app, a Roon Ready device, etc.) wants to connect.

The good news is that a NAS running 24/7 is genuinely one of the best homes for it, most NAS devices are designed for always-on use and are extremely power-efficient.

As for alternatives, if the server isn’t running before your amp even powers on, you’ll hit the same problem with any Roon-based setup. There’s no version of Roon that wakes on demand in a reliable way for playback. Your real options are essentially:

Honestly, for the use case you’re describing, unscheduled, spontaneous listening, 24/7 operation is the only setup that will feel seamless. Any sleep/wake approach is going to add friction and reliability headaches.

[connor]

Hi @jose_manuel_gallardo,

Roon is cross-platform, so you can always migrate to a Windows, Mac, or Linux computer in this environment if you prefer more user-friendly interface controls and power scheduling. This thread will close without any further responses so please let us know if we can assist further in the meantime. Thank you!

[connor]

Hi @jose_manuel_gallardo,

As a reminder, you can post in Roon Software Discussion anytime moving forward if you’d like suggestions for your setup.

If you require additional assistance from tech support, please reach out here.

Thank you and happy listening!