App does not work correctly when music-assistant is behind reverse proxy

[SammyMcFly]

First of all thank you for the app. You do a great job.

I have music-assistant running in a docker container and accessing it with the app via the local IP address (say 192.168.0.10, the port is found automatically: 8095) works (apart from it saying "Music Assistant login failed. Please check your credentials.", but when I then restart the app I am logged in anyway).

Now when I try to access music-assistant with app over an URL (http://music-assistant.lan) that my reverse proxy server forwards to the same IP address as before (192.168.0.10:8095), the app says:
"Connection failed: Socket Exception: Connection refused (OS Error: Connection refused, errno = 111), address = music-assistant.lan, port = 24954"

When I specify the port (http://music-assistant.lan:80) then login works as with the local IP, however pictures do not load and I cannot play audio on the phone as it does not show up as playback device. So there is clearly something not quite right.

There is a real chance that my reverse proxy setup is not sufficient is some way. Still, the music-assistant's web interface worked fine.

I use nginx proxy manager and have the following setup:

• domain: music-assistant.lan
• forward IP address: 192.168.0.10
• forward port: 8095
• websocket support: enabled

In the custom nginx configuration i have both added and removed the following three blocks:
proxy_read_timeout 3600;
proxy_send_timeout 3600;

proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

location / {
proxy_pass http://192.168.178.12:8095;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Port $server_port;
# Websocket support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}

The logs I encountered when logging in with http://music-assistant.lan:80 are found below:
log.txt

[Szene]

Strange, I also use an reverse proxy to connect to my Music Assistant container. For me it works fine with the app.
My config is also not very complicated, but I must note that I use Nginx Proxy Manager Plus, not the normal version.

I only have thse settings active:

• Force HTTPS
• X-Frame-Option: SAMEORIGIN
• Advanced:

proxy_hide_header X-Frame-Options;
proxy_hide_header Content-Security-Policy;

add_header X-Frame-Options "" always;
add_header Content-Security-Policy "" always;

proxy_set_header Accept-Encoding "";
sub_filter 'X-Frame-Options' 'X-FRAME-ALLOW';
sub_filter '"frame-ancestors' '"frame-allow-all';
sub_filter_once off;
sub_filter_types text/html text/javascript application/javascript;

Those advanced setting were set by me because I once had issues geeting MA added as a dashboard to HA, so I'm not sure if they do the trick. Regarding websocket support btw, this option is enabled as default and cant be turned of since the last version of NPM Plus.

[SammyMcFly]

Thank you for your answer. I just tried those advanced settings, but sadly they did not change the symptoms for me. I currently do not use https, as I use it only in my local network. However, this should not change anything afaik.

From looking at the logs, I suspect that some part of the app somehow tries to talk to port 8095, which might be reported as the published port by music assistant itself. But since behind the reverse proxy the app needs to talk to port 80 or 443 instead of port 8095, if I am not mistaken.

Furthermore I wonder where these high port numbers in the error messages come from (for example: port = 33100)