How does the server work with its call back? Running in kubernetes/k3s #3103
-
I have a question about the server, in the doco here; https://music-assistant.io/installation/ under 'server notes'; The server itself hosts a very simple webserver to stream audio to devices. This webinterface must be accessible via HTTP (no HTTPS) by IP-address from local players. See the server's logging at startup to see if the server has correctly auto-detected the local IP. I find it weird that 'the players' would phone home, but Ok. Here is my problem (well, I am not sure it is a problem but lets see). I am running the server in kubernetes, I run k3s at home. I found this chart; https://artifacthub.io/packages/helm/lmatfy/music-assistant-server all good. here is a snippet of my values configuration, for some context;
Now the hostNetwork gives the pod the IP address of the node in which the pod is running on, in theory this IP could change, so I have kube-vip running on my cluster and I allocated to the service/pod a static IP, the thing is... the mass server does not know about this IP, it still starts the server up on the node ip, in this case 192.168.1.27:
So the question is..... does it matter if that IP changes (192.168.1.27)? If so, how can i tell the server what IP to use? Last question, which one of those ports does it try to connect to? 8097 or 8095? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
After some conversations on discord, leaving the answers here for future reference; The streaming server on port 8097 is a proxy of sorts, my guess is mass downloads the contents for the streaming server to serve for all the players to query (so mass gives the players this internal address to pull the stream from), this makes sense so they all have the same stream. The players need access to this port, and the IP address should not change. You can hard code the settings/ip addresses for the streaming and webserver under 'settings --> core --> /webserver|streamserver/, |
Beta Was this translation helpful? Give feedback.
After some conversations on discord, leaving the answers here for future reference;
The streaming server on port 8097 is a proxy of sorts, my guess is mass downloads the contents for the streaming server to serve for all the players to query (so mass gives the players this internal address to pull the stream from), this makes sense so they all have the same stream.
The players need access to this port, and the IP address should not change. You can hard code the settings/ip addresses for the streaming and webserver under 'settings --> core --> /webserver|streamserver/,