logitech media server doesn't work on port other than the default value.

gcmvanloon commented 1 year ago

Is your feature request related to a problem?

I own a squeezebox duet; (https://www.trustedreviews.com/reviews/logitech-squeezebox-duet-network-music-system)

I'm unable to connect my squeezebox receiver with the logitech-media-server (lms) while it is running on port 7000. As stated in the link below and on many other places, the default http port for the lms should be 9000, not 7000 and the cli port should be 9090 instead of 10059... https://superuser.com/questions/1442385/which-ports-must-be-open-on-the-server-to-use-logitech-media-server-lms-for-sq

The hardware is wired to discover the lms server on port 9000. There is no easy way, that i know of, to change this.

I tried changing the port to 9000 myself through the truenas scale UI but then the app wont start at all. It will start OK when leaving the port on 7000 though

A short extract from the app events when I had the port set to 9000:

2022-11-28 21:46:18
Startup probe failed: dial tcp 172.16.0.69:7000: connect: connection refused
2022-11-28 21:46:09
Started container logitech-media-server
2022-11-28 21:46:08
Created container logitech-media-server
2022-11-28 21:46:03
Container image "tccr.io/truecharts/logitechmediaserver:8.4.0@sha256:a22d99d15cb5cba04746aa7be636635d6b7b036901db2d1fd99a222fd64b5551" already present on machine

Describe the solution you'd like

I would like the app to work with other ports than 7000 for HTTP and 10059 for CLI. I would like the defaults to be the "normal" standard ports that are used everywhere else. Hence, even in the values.yaml on the chart's github the 9000 is mentioned in the comments. Why is it changed to 7000 instead?

Describe alternatives you've considered

Tried to set the HTTP_PORT Environment variable to no avail. I came across that idea in the values.yaml file on github:

        # Please note that the main http port always has to be a 1:1 mapping between external and internal port.
        # You can't just map it like -p 7000:9000, as Logitech Media Server is telling players on which port to connect.
        # Therefore if you have to use a different http port for LMS (other than 9000) you'll have to set the HTTP_PORT environment variable

https://github.com/truecharts/charts/blob/master/charts/stable/logitech-media-server/values.yaml

Tried to go in the lms configuration and add a remote server with the truenas' ip and port 7000 hoping the squeezebox would pick it up. Unfortunately it did not.

Additional context

scale version TrueNAS-SCALE-22.02.4 app version 8.4.0_6.0.4

I've read and agree with the following

[X] I've checked all open and closed issues and my request is not there.
[X] I've checked all open and closed pull requests and my request is not there.

gcmvanloon commented 1 year ago

After some more digging around. I found this in my server logs:

[22-11-28 21:57:46.2117] main::init (380) Starting Logitech Media Server (v8.4.0, 1669013184, Mon Nov 21 08:05:26 CET 2022) perl 5.032001 - x86_64-linux-gnu-thread-multi
[22-11-28 22:24:56.7760] Slim::Networking::Discovery::getFakeVersion (131) 
You're using a SB Controller with a buggy firmware not recognizing this version of Logitech Media Server.
Please consider patching it. Until then we'll try to play nice and return a fake version number...

See https://github.com/Logitech/slimserver/blob/public/8.0/README.md#sb-radio-and-logitech-media-server-8.

It could be very possible I suffer from a firmware bug that is unable to recognise the server's version correctly as is explained here: https://github.com/Logitech/slimserver/blob/public/8.0/README.md#sb-radio-and-logitech-media-server-8

although i don't have a sb-radio but a sb-duet I can imagine the same bug is in my device... I can't confirm until I find a newer firmware or I can install an older version of the logitech-media-server...

The original bug with port other than 7000 still stands though ;)

truecharts-admin commented 1 year ago

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists

truecharts / public