Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot connect to Hifiberry with Spotify connect #13

Open
Mrcloc opened this issue Nov 28, 2022 · 6 comments
Open

Cannot connect to Hifiberry with Spotify connect #13

Mrcloc opened this issue Nov 28, 2022 · 6 comments

Comments

@Mrcloc
Copy link

Mrcloc commented Nov 28, 2022

It will often connect fine, but half the time Spotify will say connecting, and then never connect. And from any device. I've soft restarted the Hifiberry, I've turned the Spotify source on and off, I've restarted Spotify on PC and phone, but to no avail. This will go on for a long time, and then suddenly it will decide to connect.
Issue

@ashthespy
Copy link
Owner

Would you have some logs to share from the daemon while this is happens?
You could try also to switch to credential based auth on the daemon to rule out issues with mdns..

@potatoleaf
Copy link

I have the same problem since a few weeks. Journalctl shows the following entries:

Aug 08 19:07:43 tuberadio python3[398]: INFO: audiocontrol2 - configuring watchdog spotifyd: ['spotify']
Aug 08 19:07:49 tuberadio systemd[1]: Starting Vollibrespot...
Aug 08 19:07:49 tuberadio vollibrespot[741]: vollibrespot v0.2.4 UNKNOWN UNKNOWN (librespot 1a224a3 2020-10-25) -- Built On 2023-04-04
Aug 08 19:07:49 tuberadio vollibrespot[741]: Reading Config from "/etc/vollibrespot.conf"
Aug 08 19:07:49 tuberadio vollibrespot[741]: [Vollibrespot] : Using Alsa backend with device: default
Aug 08 19:07:50 tuberadio systemd[1]: Started Vollibrespot.
Aug 08 19:07:56 tuberadio node[765]: Registering source 'spotify'...
Aug 08 19:07:57 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:57 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:58 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:59 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:59 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:07:59 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:08:00 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid
Aug 08 19:08:02 tuberadio vollibrespot[741]: [Vollibrespot] : couldn't parse packet from 192.168.0.108:5353: type 47 is invalid

Are there any other logs I could provide?

@ashthespy
Copy link
Owner

You could try also to switch to credential based auth on the daemon to rule out issues with mdns..

@innir
Copy link

innir commented Jan 2, 2024

It indeed seems to be an issue with mdns, it's reported and fixed upstream: librespot-org/libmdns#19

@Mrcloc
Copy link
Author

Mrcloc commented Jan 3, 2024 via email

@rlirli
Copy link

rlirli commented Nov 17, 2024

This issue's cause might differ from what's described here, but the symptoms match a recent discussion on the HiFiBerry forum. For anyone experiencing similar behavior, try commenting out the static DNS entry for ap-gew4.spotify.com in the HifiBerry's /etc/hosts file:

ssh [email protected]
nano /etc/hosts

Locate the line:

104.199.65.124 ap-gew4.spotify.com

And change it to:

#104.199.65.124 ap-gew4.spotify.com

Save and exit (Ctrl+O, Enter, Ctrl+X).

For more details, refer to this post: Spotify Connect doesn’t work anymore - HiFiBerryOS 20230404.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants