[Bug] 2.7.11: Sendspin server binds to specific IP instead of 0.0.0.0, proxy fails to connect on 127.0.0.1

[sz24sz24-5607]

music-assistant(1).log

What version of Music Assistant has the issue?

2.7.11

How is the MA server installed?

Home Assistant OS Addon

Mandatory: Carefully read the Troubleshooting FAQ and confirm that

• I have examined the logs and tried to resolve this issue
• I have fixed any errors or warnings 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 am not using or have disabled tools such as AdGuard, Pi-hole or pfSense and retested
• I have checked my network setup to ensure mDNS/multicast is not being blocked
• I have reviewed the Open and Closed Issues and Discussions
• I have reviewed the applicable player or music provider documentation
• I have reviewed the MA Status Page
• I have tried restarting MA and rebooting the host

As Applicable: Carefully read the Troubleshooting FAQ and confirm that

• 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
• For voice problems, I have sought help elsewhere before returning here
• For playback problems, I have recycled power to the physical device

The problem

The server binds to 192.168.178.150:8927 but the proxy connects
to INTERNAL_SENDSPIN_URL which resolves to 127.0.0.1:8927.
This worked correctly in 2.7.10 where the server bound to 0.0.0.0:8927.

Expected behavior
Sendspin server should bind to 0.0.0.0:8927 as it did in 2.7.10,
so the internal proxy can reach it via 127.0.0.1.

What is working

• UPnP/DLNA players work fine (Yamaha RX-V579)
• MA web interface loads correctly
• All music providers load correctly

What is not working

• All Sendspin players (browser PWA, MassDroid Android app)
• Players appear with loading spinner, never become available

How to reproduce

1. Have a working Music Assistant installation (HAOS App) with
   Sendspin players functioning correctly on version 2.7.10

2. Update Music Assistant App to version 2.7.11
   (either manually or via automatic update)

3. Restart the Music Assistant App

4. Open Music Assistant and navigate to Settings → Players

5. Observe that all Sendspin players show a loading spinner
   and never become available

6. Check the MA log and observe:

   • Sendspin server binds to the specific network IP (e.g. 192.168.178.150:8927)
     instead of 0.0.0.0:8927
   • sendspin_proxy immediately fails with
     ConnectionRefusedError on 127.0.0.1:8927

Music Providers

RadioBrowser, Podcast RSS Feed, Filesystem (local/remote share)

Player Providers

UPnP/DLNA (Yamaha RX-V579), Sendspin

Full log output

INFO [aiosendspin.server.server] Starting Sendspin server on port 8927
INFO [aiosendspin.server.server] Sendspin server started successfully on 192.168.178.150:8927
...
ERROR [music_assistant.sendspin_proxy] Failed to connect to internal Sendspin server
ConnectionRefusedError: [Errno 111] Connect call failed ('127.0.0.1', 8927)

Additional information

In 2.7.10 the log showed:
Sendspin server started successfully on 0.0.0.0:8927

In 2.7.11 the log shows:
Sendspin server started successfully on 192.168.178.150:8927

The internal proxy (sendspin_proxy.py line 89) always connects to
INTERNAL_SENDSPIN_URL which resolves to 127.0.0.1:8927. Since the
server no longer listens on 0.0.0.0 (all interfaces), 127.0.0.1
is unreachable and every proxy request fails immediately.

Workarounds attempted (none resolved the issue):

• Restarting the MA App multiple times
• Full Home Assistant reboot
• Clearing MA cache/data
• Removing and re-adding the HA integration for Music Assistant

The DLNA player (Yamaha RX-V579) is completely unaffected and
works normally. Only Sendspin-based players are broken.

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

2026.3.2

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Raspberry Pi

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

• Yes

[github-actions]

⚠️ Issue Template Validation

Thank you for reporting this issue! However, there are some problems with the issue template:

• Please ATTACH the log file instead of pasting it. See instructions in the template.

Please update your issue with the missing information. Providing complete information helps us resolve issues faster. See the Troubleshooting Guide for more details.

[sz24sz24-5607]

Log additional in the ticket

[sz24sz24-5607]

Workaround: In Settings → System → Streams → Advanced → "Bind to IP/interface" set to 0.0.0.0 instead of a specific IP. This allows the Sendspin proxy to reach the server via 127.0.0.1:8927.

[sz24sz24-5607]

Additional finding: Changing "Bind to IP/interface" to 0.0.0.0 fixes Sendspin but breaks DLNA/UPnP discovery (Yamaha RX-V579). There is no configuration that fixes both simultaneously. This confirms the bug is in the Sendspin server binding logic in 2.7.11.

[MarvinSchenkel]

Are you sure you hadn't accidentally changed the bind ip of the stream server before? There are literally 0 changes related to this between 2.7.10 and 2.7.11. 0.0.0.0 is the default value for the streamserver's bind interface: