Immediately shutting down discovery server

[juup]

Installed raspotify on a Raspberry Pi4 with osmc based on Debian.

When I launch librespot -n "Librespot Speaker" -b 160 -v zeroconf immediately stops and the device is not discoverable. How can I found out why?

[2023-01-21T08:40:36Z INFO  librespot] librespot 0.4.2 6db2180 (Built on 2023-01-14, Build ID: htFgTqU5, Profile: release)
[2023-01-21T08:40:36Z TRACE librespot] Command line argument(s):
[2023-01-21T08:40:36Z TRACE librespot]          n "Librespot Speaker"
[2023-01-21T08:40:36Z TRACE librespot]          b "160"
[2023-01-21T08:40:36Z TRACE librespot]          v
[2023-01-21T08:40:36Z DEBUG librespot_discovery::server] Zeroconf server listening on 0.0.0.0:34371
[2023-01-21T08:40:36Z DEBUG librespot_discovery::server] Shutting down discovery server

[kingosticks]

That log message is wrong and needs fixing, it prints as soon as the server starts. It does not actually mean the discovery server is shutting down yet!

If you are unable to see librespot in your Spotify client apps then it's a different problem.

[juup]

Ok, so how can I find out what's the problem?

If I'm running avahi-browse -at on another PC I get + enp38s0 IPv4 raspotify (osmc) _spotify-connect._tcp local But on the same PC Spotify client doesn't find it.

[juup]

Ok, so how can I find out what's the problem?

If I'm running avahi-browse -at on another PC I get + enp38s0 IPv4 raspotify (osmc) _spotify-connect._tcp local But on the same PC the Spotify client doesn't find it.

[roderickvd]

Closing but feel free to continue on the Gitter chat: https://gitter.im/librespot-org/spotify-connect-resources

Other than that cosmetic thing with the erroneous message, this is a network configuration thing and most likely no librespot bug.