07-27-2022, 06:21 AM
(07-26-2022, 09:52 PM)Ja Tim Curtis Wrote:(07-26-2022, 06:52 PM)roderickvd Wrote: I will make some time and soon do a librespot point release to blacklist this broken access point. Are there more defunct APs that any of you have encountered? If so please add them to this issue: https://github.com/librespot-org/librespot/issues/972
Edit: fix is here: https://github.com/librespot-org/librespot/pull/1026
Please verify and I can do a release the coming few days.
Many thanks :-)
After you release it will take our project a few weeks to build, test and publish a new librespot package. Are there recommended workarounds that users can try in the meantime?
I've seen a couple but have not tried them myself.
1. Add --ap-port=[some random port] to librespot launch params.
2. Add 0.0.0.0 apresolve.spotify.com to the file /etc/hosts
Yes, both will work. For the first the random port must not be 4070, 443 or 80.