Music Assistant
accessing music assistant remotely (own domain) #5453
-
|
I expose many of my containers through cloudflare (and pangolin) so I can access them remotely using my own domain. (https://music.mydomain.com) This works great with all my containers, but music assistant shows me this for some reason. 
Is there some special configuration I must do with music assistant? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Perhaps look at the built in remote access feature. I cant assist with yorur existing setup. |
Beta Was this translation helpful? Give feedback.
-
|
That requires an additional authentication step though. What does the screenshot above mean? Why isnt music assistant unable to find its own server address? |
Beta Was this translation helpful? Give feedback.
-
|
Looks like a problem with your reverse proxy config. MA isn't able to complete the WebSocket handshake back to the server through your Cloudflare/Pangolin tunnel |
Beta Was this translation helpful? Give feedback.
-
|
My setup also has the same subdomain configuraiton as you, it works flawlessly (the build in remote access feature doesn't really work in my case due to some network provider limitations I think). I have it proxied via Nginx Proxy Manager with Websocket support enabled. |
Beta Was this translation helpful? Give feedback.
My setup also has the same subdomain configuraiton as you, it works flawlessly (the build in remote access feature doesn't really work in my case due to some network provider limitations I think). I have it proxied via Nginx Proxy Manager with Websocket support enabled.
Additionally in MA itself, I have set my base URL to the same subdomain in Settings > System > Webserver, you might want to check if that is also correctly set.