Troubleshooting · Discovery and visibility

Spotify Connect not showing? Fix discovery issues first.

If your Spotycast or spotifyd device does not appear in the Spotify app, the root cause is usually discovery and network visibility: mDNS / Zeroconf, Docker network mode, firewall rules, Wi-Fi isolation, VLAN separation, or a spotifyd publishing issue.

This is not an audio-path problem yet. Before troubleshooting Icecast, Liquidsoap, codecs or players, confirm that the Spotify-facing device is actually visible on the local network.

Check installation
Spotify Connect still broken?
Spotify Connect not showing spotifyd not visible mDNS / Zeroconf Docker host mode
Related guides: No audio, Dropouts, Metadata.

Quick answer

A Spotify Connect device that does not appear is usually not an audio-path issue yet. It is most often a local discovery issue. Before touching codecs, outputs, or Icecast behavior, verify that spotifyd is running, the host is reachable on the LAN, and Zeroconf discovery is not blocked by Docker, Wi-Fi isolation, VLANs, or firewall rules.

In many installations, the fastest win is to use host network mode for the container and make sure the Spotify controller device is on the same local network as the Spotycast host.

Typical symptoms

Device missing in Spotify

The Spotycast or spotifyd target never appears in the list of available playback devices.

Device appears then disappears

Discovery is unstable, often because of mDNS filtering, subnet separation or unreliable container networking.

Service alive but invisible

spotifyd is running locally, but discovery packets do not reach the controller device correctly.

Why Spotify Connect devices stop appearing

Spotify Connect discovery depends on a clean local-network path between the publishing service and the controller device. If multicast discovery is filtered, the device may be healthy on the host but still invisible in the Spotify app.

  • Docker bridge networking can interfere with discovery visibility
  • mDNS / Zeroconf packets may be blocked or not forwarded correctly
  • Phone and host on different SSIDs, VLANs, or subnets may prevent discovery
  • Guest Wi-Fi or AP client isolation can stop local device visibility
  • Firewall rules may block local reachability or discovery traffic
  • spotifyd misconfiguration can prevent correct device publication
  • Restart loops or backend failures may make the device appear intermittently
If the device is visible but playback is silent, that is a different issue class. Use No audio instead.

How to diagnose the issue

01 · Service Check spotifyd Confirm the service is running and not restarting continuously.
02 · Docker Prefer host networking For discovery, host mode is usually more predictable than bridged networking.
03 · LAN Same network segment Avoid guest Wi-Fi, AP isolation, subnet separation and broken multicast forwarding.
04 · Config Review publishing settings Backend, name, credentials and Zeroconf behavior all affect visibility.

1. Confirm spotifyd is running

A missing device can simply mean the publishing service never started or is restarting continuously.

2. Prefer Docker host networking

For Spotify device discovery, host mode is usually much more predictable than bridged container networking.

3. Keep controller and host on the same LAN

The Spotify app on your phone, tablet or desktop must be able to discover the publishing host directly.

systemctl status spotifyd
journalctl -u spotifyd -n 100 --no-pager

# Docker Compose hint
network_mode: host

Network checks

  • Prefer the same subnet for the Spotify app and the Spotycast host
  • Avoid guest Wi-Fi isolation
  • Disable AP client isolation if active
  • Check that mDNS is not filtered across SSIDs or VLANs
  • Temporarily test from a wired or same-SSID controller if possible

Review spotifyd publishing settings

Broken auth, a backend mismatch, invalid config, or broken service startup can leave the service alive but unpublished or unusable. 

device_name = "Spotycast"
backend = "pulseaudio"
bitrate = 320
zeroconf_port = 0

Restart the stack cleanly after changes

systemctl restart spotifyd
systemctl restart pulseaudio

What to collect in logs

If the issue persists, collect a compact diagnostic bundle before changing more variables. For a discovery problem, logs and network topology are usually more useful than screenshots of the Spotify app alone. 

journalctl -u spotifyd -n 200 --no-pager
docker logs <container_name> --tail 200
ip addr
ip route
Include the deployment mode, whether Docker uses host networking, whether the Spotify controller is on the same subnet, and whether guest Wi-Fi, VLANs, firewall rules or AP isolation are involved.

When this is not just a discovery problem

If the device appears correctly in Spotify but playback never starts, starts silently, or drops after a few seconds, the issue is no longer “not showing”. At that point, move to the broader incident path.

How Spotycast fits into the fix

Spotycast separates the Spotify-facing control layer from the downstream HTTP stream consumed by players. But discovery still matters at the beginning of the chain: if the Spotify app cannot see the Spotycast or spotifyd endpoint, there is no playback session to capture and publish.

How Spotycast works How to install Spotycast Spotify to Icecast Spotify Connect not working

Frequently asked questions

Why does Spotify Connect not show my device?

In most cases, the reason is a discovery failure: mDNS or Zeroconf packets do not reach the Spotify controller correctly, or spotifyd is not publishing the device as expected.

Does Docker bridge mode break Spotify discovery?

It often makes discovery less predictable. For this use case, host networking is usually the most reliable option.

Can firewall rules prevent the device from appearing?

Yes. Discovery visibility and host reachability can both be affected by firewall policy, guest Wi-Fi isolation, VLANs, or subnet segmentation.

What if the device appears but playback still fails?

Then discovery is no longer the main issue. Move to the broader guide at Spotify Connect Not Working, or use the dedicated troubleshooting pages for no audio or dropouts.

Fix visibility before debugging audio.

If the Spotify app cannot see the device, stay on the discovery layer: spotifyd service state, Docker host networking, local subnet, mDNS / Zeroconf, firewall rules, VLANs and Wi-Fi isolation. Once the device appears, then move on to audio, buffering or metadata troubleshooting if playback still fails.

Spotify Connect Not Working How to install No audio Dropouts Metadata Support