Replies: 1 comment
-
That is not a "metadata" page it is the CORE modules. Hopefully this steers you in the right direction |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have installed MASS as a Docker container on a raspi, which has two network interfaces, the normal eth0 and a wireguard endpoint wg0.
After starting, MASS uses the IP address of wg0, but this is not accessible for other nodes in the local network. Instead, MASS should use the "normal IP address" (eth0).
In the log file I see IP address of wg0 as part of the media_content_id sent in the play_media service to the media players.
I have read the documentation (troubleshooting-page) , but I don't understand exactly what I am supposed to do.
On my settings page, which can be accessed via the gear-icon at the top right of the home page, there are only settings for provider data (music, player, metadata, plugins). Cannot see any "core settings".
Starting the docker container with a environment variable "PUBLISHED_IP_ADDRESS="does not help either.
This is my docker file:
What am I doing wrong?
As a workaround, I start the MASS container first and only then set up the VPN tunnel. Then it works.
Beta Was this translation helpful? Give feedback.
All reactions