49 minutes ago, jademonkee said:

Dang.

Looks like it's gonna be a long troubleshooting session 🫠

I'm doing some testing. I have a new Squeezebox Radio that can't see the LMS. Try setting the Network type to 'Host'.

On 5/1/2026 at 9:20 PM, dlandon said:

I'm doing some testing. I have a new Squeezebox Radio that can't see the LMS. Try setting the Network type to 'Host'.

Can confirm: I had LMS as Bridge, and setting it to Host fixed the problem. So all good now.

It seems that Docker 28+ broke UDP broadcast forwarding into bridge containers, which kills Slimproto discovery and connectivity for Squeezebox Radio / PiCorePlayer.

So switching to Host is now considered best practice for LMS (indeed, I note that this container defaults to Host, but I have been using various LMS containers for so long that I continued to use Bridge).

23 hours ago, jademonkee said:

Can confirm: I had LMS as Bridge, and setting it to Host fixed the problem. So all good now.

It seems that Docker 28+ broke UDP broadcast forwarding into bridge containers, which kills Slimproto discovery and connectivity for Squeezebox Radio / PiCorePlayer.

So switching to Host is now considered best practice for LMS (indeed, I note that this container defaults to Host, but I have been using various LMS containers for so long that I continued to use Bridge).

I just changed the default. LMS has been set to Bridge forever.

On 5/3/2026 at 12:21 PM, jademonkee said:

Can confirm: I had LMS as Bridge, and setting it to Host fixed the problem. So all good now.

Thanks a lot, this worked for me too.

Autodiscovery was not working after the upgrade to Unraid 7.2.5, this fixed it.

@dlandon
Version 9.1.1 is out. Can you please do a refresh of the Docker image?

Many thanks!

If anyone is interested, the changelog is here:

GitHub

Commits · LMS-Community/slimserver

Server for Squeezebox and compatible players. This server is also called Lyrion Music Server. - Commits · LMS-Community/slimserver

EDIT: Better, more readable, changelog here:

https://lyrion.org/getting-started/changelog-lms9/

Edited June 22Jun 22 by jademonkee

2 hours ago, jademonkee said:

@dlandon
Version 9.1.1 is out. Can you please do a refresh of the Docker image?

Many thanks!

If anyone is interested, the changelog is here:

GitHub

Commits · LMS-Community/slimserver

Server for Squeezebox and compatible players. This server is also called Lyrion Music Server. - Commits · LMS-Community/slimserver

Done.

Not sure what broke but I can no longer get the Spotify plugin to work on my setup. Only changes would be docker image update and Spotify plugin update.

This is the error I see in the log file - [26-08-27 09:51:09.2526] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling Slim::Web::HTTP::processHTTP: read_file '/config/cache/spotty/__AUTHENTICATE__/credentials.json' - sysopen: Permission denied at /config/cache/InstalledPlugins/Plugins/Spotty/AccountHelper.pm line 323.

; fh=Slim::Web::HTTP::ClientConn=GLOB(0x5579fcc71138)

[26-08-27 09:51:09.9731] Slim::Control::Request::execute (1884) Error: While trying to run function coderef [Slim::Control::Queries::statusQuery]: [read_file '/config/cache/spotty/__AUTHENTICATE__/credentials.json' - sysopen: Permission denied at /config/cache/InstalledPlugins/Plugins/Spotty/AccountHelper.pm line 323.

]

Has anyone else seen this issue?

I asked the spotify guy if he knew why the json file gets created as root

ls -la /mnt/cache/appdata/LyrionMusicServer/cache/spotty/__AUTHENTICATE__/
total 4
drwxr-xr-x 2 nobody users  30 Aug 28 13:41 ./
drwxr-xr-x 3 nobody users  30 Aug 28 13:41 ../
-rw------- 1 root   root  321 Aug 28 13:41 credentials.json

It writes as the user LMS is run as. I'm surprised this would be root,
as we try to refuse to do this. Might have to do with the Docker image
you're using.

Edited August 29Aug 29 by chip

3 hours ago, chip said:

It writes as the user LMS is run as. I'm surprised this would be root,
as we try to refuse to do this. Might have to do with the Docker image
you're using.

Give me the output of these commands:
docker exec LyrionMusicServer ls -ld /config /config/cache

and

docker exec LyrionMusicServer ps -eo user,pid,ppid,args

Edited August 29Aug 29 by dlandon
Fix command.

docker exec LyrionMusicServer ls -ld /config /config/cache

drwxrwxr-x 6 nobody users 61 Feb 5 2025 /config

drwxrwxr-x 10 nobody users 4096 Aug 30 09:45 /config/cache

docker exec LyrionMusicServer ps -eo user,pid,ppid,args

docker exec LyrionMusicServer ps -eo user,pid,ppid,args

USER PID PPID COMMAND

root 1 0 /usr/bin/python3 -u /sbin/my_init

root 36 1 /usr/sbin/syslog-ng --pidfile /var/run/syslog-ng.pid -F --no-caps

root 663 1 /usr/bin/runsvdir -P /etc/service

root 664 663 runsv sshd

root 665 663 runsv lyrionmusicserver

root 666 665 /bin/bash ./run

nobody 668 666 /usr/bin/perl /usr/sbin/squeezeboxserver --u nobody --prefsdir /config/prefs --logdir /config/logs --cachedir /config/cache --httpport 9000

nobody 669 668 /usr/bin/perl /usr/sbin/squeezeboxserver-resized

nobody 712 668 /config/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c /config/cache/spotty -n Spotify Authorization (Lyrion Music Server (Docker)) --authenticate

root 745 0 ps -eo user,pid,ppid,args

14 minutes ago, chip said:

docker exec LyrionMusicServer ls -ld /config /config/cache

drwxrwxr-x 6 nobody users 61 Feb 5 2025 /config

drwxrwxr-x 10 nobody users 4096 Aug 30 09:45 /config/cache

docker exec LyrionMusicServer ps -eo user,pid,ppid,args

docker exec LyrionMusicServer ps -eo user,pid,ppid,args

USER PID PPID COMMAND

root 1 0 /usr/bin/python3 -u /sbin/my_init

root 36 1 /usr/sbin/syslog-ng --pidfile /var/run/syslog-ng.pid -F --no-caps

root 663 1 /usr/bin/runsvdir -P /etc/service

root 664 663 runsv sshd

root 665 663 runsv lyrionmusicserver

root 666 665 /bin/bash ./run

nobody 668 666 /usr/bin/perl /usr/sbin/squeezeboxserver --u nobody --prefsdir /config/prefs --logdir /config/logs --cachedir /config/cache --httpport 9000

nobody 669 668 /usr/bin/perl /usr/sbin/squeezeboxserver-resized

nobody 712 668 /config/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c /config/cache/spotty -n Spotify Authorization (Lyrion Music Server (Docker)) --authenticate

root 745 0 ps -eo user,pid,ppid,args

Thanks for the information. The process listing confirms that LMS and the Spotty authentication process are both running as nobody:

nobody 668 ... /usr/bin/perl /usr/sbin/squeezeboxserver --u nobody ...
nobody 712 ... /spotty-x86_64 ... --authenticate

The /config and /config/cache directories are also correctly owned by nobody:users.

So the Docker container appears to be setting the ownership and running LMS correctly. I don't see anything at the container level that would explain why Spotty's credentials.json is being created as root:root.

I'd suggest continuing this with the Spotty developer since the Spotty authentication process itself is running as nobody.

My issue was with The spotty Helper Binary Crash / Executable Flag

Spotty uses a standalone helper binary (compiled for Linux x86_64) to handle Spotify's auth and decryption. If that binary lacks executable permissions, crashes due to missing GLIBC libraries, or gets blocked by Unraid's mount flags, it fails quietly during login and never writes the key files.

That is the culprit! The helper: '' setting means Spotty has no path configured for its backend helper binary.

Stop the DOCKER

Edit spotty.prefs Directly

Update helper: '' to point directly to the binary path inside the container:

Restart Docker

It worked now............