Connection Problems

Connection Refused

Symptom: “Connection refused” error when trying to connect.

Causes and Fixes:

1. Server not running — Start your SendSpin or Music Assistant server
2. Wrong port — Verify the port number (default: 8927)
3. Firewall — Ensure port 8927 is open on the server’s firewall
4. Wrong IP address — Verify the server’s current IP (it may change with DHCP)

Connection Timeout

Symptom: Connection attempt hangs and eventually times out.

Causes and Fixes:

1. Different networks — Ensure your device and server are on the same subnet
2. VPN interference — Disable VPN if it routes local traffic through an external tunnel
3. AP isolation — Some WiFi setups isolate clients from each other. Check your router settings.

Frequent Disconnections

Symptom: Connection drops repeatedly and the app shows “Reconnecting…”

Causes and Fixes:

1. Weak WiFi signal — Move closer to your access point or add a repeater
2. Battery optimization — Exempt SendSpin Player from battery optimization in Android Settings
3. Android Doze — Enable High Power Mode in app settings for always-on devices
4. Server overload — Check server logs for errors
5. Network congestion — Try switching to Opus codec to reduce bandwidth

Auto-Reconnection

The app automatically tries to reconnect when a connection drops:

• Normal mode — Retries with exponential backoff up to a limit, then gives up
• High Power Mode — Retries indefinitely with a 30-second steady-state interval

A “Reconnecting…” banner appears on screen during reconnection attempts.

Remote Access Issues

Remote ID Not Connecting

1. Verify the 26-character Remote ID is correct (uppercase letters and numbers only)
2. Check that Remote Access is enabled in your Music Assistant settings
3. Ensure your server has internet access for the WebRTC relay
4. Try regenerating the Remote ID in Music Assistant settings

Proxy Authentication Failed

1. Verify your username and password (or token)
2. Check that your proxy server is running and accessible
3. Verify the proxy URL is correct, including the path
4. Check proxy server logs for authentication errors
5. If using token mode, the token may have expired — generate a new one

mDNS Discovery Not Working

Symptom: Nearby servers list stays empty even though the server is on the same network.

Causes and Fixes:

1. Router blocks multicast — Many enterprise and some consumer routers block mDNS. Use manual entry instead.
2. Guest network — Guest networks typically isolate devices. Connect to the main network.
3. Multiple VLANs — mDNS doesn’t cross VLAN boundaries without a reflector/proxy
4. Server not advertising — Check that your server’s mDNS/Zeroconf service is running

Manual entry always works as a fallback — you just need the server’s IP address and port.

Diagnostic Steps

If none of the above solve your issue:

1. Test from another device — Can another client connect to the server?
2. Test the network — Can you ping the server’s IP from your Android device?
3. Check server logs — Look for connection attempts and errors on the server side
4. Enable debug logging — Collect logs from the app and file a bug report