brawny

Roon Lifetime subscriber here as well. Been using your template for a few months now without issue. I'll let you know if anything breaks, as I use Roon daily as well. 🎶

Totally understand. I'm an IT guy too - but no experience with dockers other than installing and configuring. Usually with the help of SpaceInvaderOne videos... Curious - the logging for roonserver is pretty sparse - not even any date/timestamps. How will we know if/when the update happens? ChatGPT can be helpful, but for me it typically gets me in over my head, and then switches models because I've used up my 'free' allotment. The models get dumber by the hour, and before I know it I've f*cked up my networking or something...

Wanted to say that I couldn't resist - I've updated to mackid1993/docker-roonserver:latest, and restarted my docker. Working fine, so far... :-)

If the current docker isn't being maintained any more, I'd be interested in trying yours @mackid1993, but want to be able to use it from within Apps, rather than modifying the docker parameters to point to your repository. Not sure how that gets done, but I'll be following. Thanks for taking an interest in keeping this docker up to date. I'm new to Roon within the last year, but went all in with a lifetime membership. Being able to run roonserver on my unraid box is really slick!

I see the same warning in my server log: avahi-daemon[3985]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** and the same output from the "lsof -i -P -n | grep 5353" command: avahi-dae 3985 avahi 14u IPv4 39789328 0t0 UDP *:5353 RoonAppli 24329 root 276u IPv4 71818202 0t0 UDP *:5353 RoonAppli 24329 root 278u IPv4 71818204 0t0 UDP *:5353 RoonAppli 24329 root 280u IPv4 71818206 0t0 UDP *:5353 Roon is working fine, as is Roon Arc, but my Roon log shows these errors: Should I be concerned?

I just had this happen last night. UnRaid 6.9.2. Rebooted the server this morning, and it came back up fine, and started a parity check. I've enabled the syslog, so hopefully if it happens again, I'll have a clue as to cause. I haven't changed anything on the server in quite some time. The only recent change was to enable a plugin for the Logitech Media Server docker for "shairTunes" a few days ago.

See if this works for you. For some reason the IP address SAB was using internally changed for me. Not something I did myself... The quote above is how I found and resolved it.

I figured out my issue, but its strange that it popped up today, and the resolution wasn't what I expected. I normally follow Space Invader One's videos for setting dockers up rather than reinventing the wheel. That's what I did with SABnzbd, Radarr and Sonarr. This morning the issue I was having was that Sonarr and Radarr couldn't communicate with SABnzbd. They've been working for over a year, without issue. Yesterday I lost all my dockers and had to restore from a backup, so somehow that might be part of what caused the issue - not sure. To resolve, I noticed that when I looked at "Status and Interface Options" in the SABnzbd UI, the local IPV4 address was a 10.8.x.x address. I had this set as the 192.168.1.x address of my server in Radarr and Sonarr (and I'm sure this is how it has always been!). I copied/pasted the 10.x.x.x address into the SAB config in Sonarr and Radarr, and lo and behold, they were able to connect and started to work... Not sure how this happened, but glad it is...

Any luck getting this resolved? I'm having a similar issue with my setup as of this morning following some changes to my system.

Posted this in General Support - cross posting the link here in case its useful.

I did. Post and response is here: Logitech Media Server forums The response was: This really is the hostname, given by the underlying system. But you can change LMS' name to something else in the Basic Settings/Media Library Name. Please note that this would change the name shown in apps, but not eg. the URL you'd have to use to access LMS. I've made this change within the app in [Basic Settings -> Media Library Name]. Fixed!

Hopefully a simple question, but I haven't been able to figure out how to change the hostname of my LMS docker. Would like to have something a little more friendly than "14f53de05a80" show up in iPeng, and SqueezePlay, etc... Thanks in advance! Brawny

Problem resolved. I had not restarted Unraid, but we had a thunderstorm last night, and the power went out. I don't have my server on a UPS yet, so it power cycled. The root cause was a misconfiguration in the proxy port for Sonarr. I had it set for 8181 instead of 8118. Comparing the configuration data between Sonarr and Radarr helped me find it. I think there was an issue with pihole initially, and restarting Unraid would have resolved the issue, but because I removed/reinstalled/reconfigured Sonarr - and didn't have the proxy port set correctly, restarting Unraid didn't resolve the issue. I'm good to go now - all dockers are working properly. Thanks for your help with this! Brawny

Hoping this is the right place to post this. I'm new to Unraid and Docker, as well as Sonarr. I am using Sickbeard on an older server still, and in the process of migrating to a new Unraid server. The story to date: I've successfully installed Unraid 6.7.0, and configured it successfully, using Spaceinvader One's videos when needed. I've installed Community Apps, and the following Dockers in this order: binhex-krusader LogitechMediaServer binhex-sabnzbdvpn binhex-radarr binhex-sonarr binhex-lidarr binhex-plex musicbrainz pihole Everything worked properly until some time shortly after deploying pihole. I'm now getting an error - but only from sonarr about connectivity: System.Net.WebException: Error: ConnectFailure (Connection refused): 'http://services.sonarr.tv/v1/update/master/changes?version=2.0.0.5338&os=linux&runtimeVer=5.20.1' ---> System.Net.WebException: Error: ConnectFailure (Connection refused) ---> System.Net.Sockets.SocketException: Connection refused at System.Net.Sockets.SocketAsyncResult.CheckIfThrowDelayedException () [0x0003b] in /build/mono/src/mono/mcs/class/System/System.Net.Sockets/SocketAsyncResult.cs:134 at System.Net.Sockets.Socket.EndConnect (System.IAsyncResult asyncResult) [0x0002c] in /build/mono/src/mono/mcs/class/System/System.Net.Sockets/Socket.cs:1150 at System.Net.Sockets.SocketTaskExtensions+<>c.<ConnectAsync>b__2_1 (System.IAsyncResult asyncResult) [0x00000] in /build/mono/src/mono/mcs/class/System/System.Net.Sockets/SocketTaskExtensions.cs:35 at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00019] in /build/mono/src/mono/external/corert/src/System.Private.CoreLib/src/System/Threading/Tasks/FutureFactory.cs:538 --- End of stack trace from previous location where exception was thrown --- Screenshot of most recent System/Status/Logs tab: I suspect that something network-related is misconfigured either in sonarr, or pi-hole, but I'm not sure what that could be. Steps I've taken so far: Remove pihole as my DNS server on my router (Unifi USG). No change. Restart sonarr. No change. Remove sonarr and re-install. No change. Pihole seems to be working properly, as do sabnzbdvpn, radarr and plex, and all other devices on my lan. Any suggestions on troubleshooting would be really appreciated. Thanks! Brawny