Music Assistant frontend not respondig after multiple changes in short term

[frigi83]

What version of Music Assistant has the issue?

2.3.6

What version of the Home Assistant Integration have you got installed?

2025.1.2

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

• Yes

The problem

The interface is no longer responding (no http error like 503, 40x, ...) and the playing song end short after (I suppose is due to the cache).

How to reproduce

1. continue changing songs or albums
2. or go forward or backward in the queue
3. if you have multiple people doing that on different players, it happens quicker and more frequently

• I can reproduce it on my PC and on a smartphone, accessing MA trough a reverse proxy or directly to the IP address (see below for more information about my setup).
• After a restart of the container it works again
• if we do not apply multiple frequent actions for selecting the music in the MA player it can works for days

Music Providers

Open Subsonic (Gonic)

Player Providers

Sonos (S2)

Full log output

_music-assistant_logs.txt

Logs are from Portainer, because when the interface freeze is no longer accessible and after a restart the log is wiped.

Additional information

My configuration is as follow:

• Music Assistant runs on docker (host mode) in the same network as the Sonos speakers
• I have a reverse proxy (traefik) for https, but I can reach MA with the IP
• Home Assistant runs on a Raspberry 4 (with 4G)
• I cannot test with the add-ons in Home Assistant, because it is in another network

What version of Home Assistant Core are your running

2025.1.2

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Raspberry Pi

[TooMuchBull]

Not sure if this helps, but I have found that if I use rewrite, I can still get in with TLS through NGINX. EG:

    location /musicassistant-server/ {
        rewrite ^/musicassistant-server(/.*)$ $1 break;
        proxy_pass http://127.0.0.1:8095/;
        proxy_set_header Host 127.0.0.1;
        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;

        # WebSocket Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        # Timeout Adjustments
        proxy_read_timeout 60s;
        proxy_send_timeout 60s;
    }

But I have not been able to get it working behind a reverse proxy without doing this.