raspotify: Setting up dns-sd failed
Compatible Device
- I’m running Raspotify on a compatible Device
Compatible OS
- I’m running Raspotify on a compatible OS
Latest Version
- I’m running the latest version of Raspotify
Due Diligence
- I have done my due diligence
What happened?
Hi!
Thanks for the great library. I’ve been trying to get raspotify to work again, after upgrading to debian bullseye, but have been running into same issue again and again.
I’ve added the relevant log line below, but there seems to be an issue in the underlying librespot library.
I’ve look around and this issue seems related/relevant, so I’ve followed the steps from there:
cargo build --release --features with-dns-sd
For compilation I had to install cargo. During compiling I had to install librust-alsa-sys-dev and install libavahi-compat-libdnssd-dev. Respectively:
curl https://sh.rustup.rs -sSf | sh
sudo apt install librust-alsa-sys-dev libavahi-compat-libdnssd-dev
After doing this, the issue is still there. Have you encountered this issue before or do you know of a solution? Might this be IPv6 related?
I did not include the syslog, as it did not yield any useful info related to this issue.
Oh and I am running this on a RaspberryPi4:
Linux raspberrypi 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Relevant log output
Mar 30 21:57:23 raspberrypi librespot[495]: [2022-03-30T20:57:23Z ERROR librespot] Discovery Error: Setting up dns-sd failed: No such device (os error 19)
Mar 30 21:57:23 raspberrypi systemd[1]: raspotify.service: Main process exited, code=exited, status=1/FAILURE
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (6 by maintainers)
@pimvh I’ve been having the same issue you described here. @JasonLG1979 This happened with the packaged version from the
apt-repository, no custom compiled version. I’m on Raspbian 11, up-to-date packages at this time, RPi4.In my case the problem was a wireguard interface on my system that was routing all the traffic through that interface, meaning the peer-configuration in the wireguard-config contained
Allowed IPs = 0.0.0.0/0. This somehow caused thedns-sd-component not being able to register andlibrespotcrashing. I don’t see this as a direct issue with raspotify or librespot, more of a combination of the this software and how wireguard interfaces/routing works. As soon as i changedAllowedIPsin the wireguard-config to restrict it to some address-ranges raspotify/librespot started working flawlessly again. You probably don’t want to make thelibrespot-service available through your tunnel anyway.Just wanted to leave this information here in case anybody else has a similar setup.