MA 2.7.3: iOS login problems and HA provider not reconnecting

[Liabs]

What version of Music Assistant has the issue?

2.7.3

How is the MA server installed?

Docker Container

Carefully read the Troubleshooting FAQ and confirm that

• I have examined the logs and tried to resolve this issue
• I have fixed any errors in the logs that relate to tags
• I am not running MA across a VPN, VLAN, subnet, behind a firewall, or using local SSL or have any other complex network setup
• I have disabled tool such as AdGuard, Pi-hole or pfSense and retested
• I have checked my network setup to ensure mDNS/multicast is not being blocked
• If using HA, I have confirmed the internal URL is set correctly
• I have tried a wired connection for issues related to interrupted or poor playback quality
• If the problem relates to a device then I have checked the device settings
• If it is a frontend issue, I have tried a different widely used browser
• I have reviewed the applicable player or music provider documentation
• For voice problems, I have sought help elsewhere before returning here
• For playback problems, I have recycled power to the physical device
• I have tried restarting MA and rebooting the host

Have you reviewed the Open and Closed Issues and Discussions to resolve this yourself?

• Yes

The problem

Setup:

• Music Assistant 2.7.3 (container install, host mode)
• Home Assistant 2026.1.1 (container install, bridge mode)
• All containers run on Synology NAS
• Accessing MA via HA iOS app (2026.1.1) and Safari on iOS (26.1)
• No container crashes or unwanted restarts
  Issues:
• HA iOS app: MA credentials never persist — every load shows the MA login screen, no session retention.
• HA iOS app: “Sign in with Home Assistant” always fails with “Invalid redirect URI.” Internal URL: http://server IP:8123
• Safari + HA iOS app: After reconnecting or app switching, MA loads but playback fails with “Please call connect first” until the HA provider is manually reloaded in MA settings.

Login, authentication and playback all happen without fail on laptop using MA via HA Lovelace sidebar on Edge browser (or as standalone http://server IP:8095 in Edge browser). MA voice control is working via HA Voice PE wired to smart speaker.

I have restarted, MA and HA containers, reauthenticated HA provider. The issues still persist.

My log in/ call connect issues appeared after updating MA container to 2.7.3. Beforehand, all I needed to do was select MA from HA sidebar in iOS, select player, start playback. Any help would be much appreciated, have I missed setting something up post-update?

The update to 2.7 is great, my constant log in and provider reloads are a barrier to quick access.

MA logs attached.

How to reproduce

Open home assistant companion app, open Music Assistant from sidebar. MA credentials required for log in. "sign in with Home Assistant" results in "Invalid redirect URI" every time.

Once signed in via HA app or standalone Safari tab: Attempting playback always results in "Please call connect first". This requires reloading HA provider before playback is possible.

Music Providers

Home Assistant provider.

Player Providers

Home Assistant Media Players (HA Voice PE and Sony Bravia): Call connect first. Web (Browser on iPhone): Says playing, no sound. Web (Safari on iPhone): Plays.

Full log output

music-assistant.log

Additional information

N/A

What version of Home Assistant Core (if used) are your running

2026.1.1

What type of installation are you running?

Home Assistant Container

On what type of hardware are you running?

Generic x86-64 (e.g. Intel NUC)

Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot

• Yes

[MarvinSchenkel]

Sounds like there's something in your docker setup that might be causing these connection issues. As a test, have you tried running the HA container in host mode to see if that helps?

[MarvinSchenkel]

Possibly related: #4867

[Liabs]

Sounds like there's something in your docker setup that might be causing these connection issues. As a test, have you tried running the HA container in host mode to see if that helps?

Thanks MarvinSchenkel. I tried your suggestion.

Host‑mode HA test

• Duplicated the existing HA container in Synology Container Manager
• Changed the duplicate’s network mode to Host
• Stopped the original (bridge‑mode) HA container
• Started the host‑mode HA container using the same /config volume

Music Assistant behaviour with HA in host mode:
MA still shows the same HA provider issues as before:

• HA provider drops / requires manual reload

MA still shows two separate iOS login problems:

• MA credentials have to be entered every time in iOS
• “Login via Home Assistant” option fails with “incorrect URI”

Restarting MA container does not resolve any of the above.

Switching HA from bridge to host mode made no difference to my:

iOS login behaviour or HA provider stability.

MA compose settings, in case I made any mistakes here:

services:
  music-assistant-server:
    image: ghcr.io/music-assistant/server:latest
    container_name: music-assistant-server
    network_mode: host
    cap_add:
      - DAC_READ_SEARCH
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined
    volumes:
      - /volume1/docker/music-assistant-config:/data
      - /volume1/music:/mnt/music
    restart: unless-stopped
    environment:
      # Provide logging level as environment variable.
      # default=info, possible=(critical, error, warning, info, debug)
      - LOG_LEVEL=info

[MarvinSchenkel]

Did you reconfigure the HA provider after switching the container? The easiest way to test this is to just change your existing HA container to network_mode: host to ensure it is configured equally.

[Liabs]

Did you reconfigure the HA provider after switching the container? The easiest way to test this is to just change your existing HA container to network_mode: host to ensure it is configured equally.

I just restarted host HA container and MA container, then re-authenticated HA provider: The "Call connect first" message hasn't re-appeared yet in MA sidebar of HA iOS app or http:/IP address:8095 (which auto logs-in). This seems to be one issue resolved.

MA credentials still always required via MA sidebar of HA iOS app + cannot log-in with HA from this route.

[OzGav]

I assume you are using an iframe. I believe you will need to use a token to persist the login in that scenario. (Similar https://github.com/orgs/music-assistant/discussions/4631)

[MarvinSchenkel]

• When you click the MA item in the HA menu bar, it should auto log you in with the current HA user. No click on 'Login with HA' should be required. This is only required when you go to http:/IP address:8095 (outside of HA context) and want to login with HA.

Would also be helpful if you shoot a video to show the issue