[GH-ISSUE #278] Librespot connection issue

kerem commented

2026-02-27 19:29:18 +03:00

Owner

Originally created by @t0k4rt on GitHub (Dec 6, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/278

Hello all,
I'm seeking guidance about a network issue.
I got a router hardware upgrade from my isp.
Since then I cannot connect.
My internal newtork has ipV6, I disabled it but it changed nothing

My questions:
Is there any debug mode for librespot ?
What tool could I use to debug this ?
Can it be a NAT traversal problem ?
Does spotify connect uses upnp ?

thanks for your insights

Originally created by @t0k4rt on GitHub (Dec 6, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/278 Hello all, I'm seeking guidance about a network issue. I got a router hardware upgrade from my isp. Since then I cannot connect. My internal newtork has ipV6, I disabled it but it changed nothing My questions: Is there any debug mode for librespot ? What tool could I use to debug this ? Can it be a NAT traversal problem ? Does spotify connect uses upnp ? thanks for your insights

kerem closed this issue

2026-02-27 19:29:18 +03:00

kerem commented

2026-02-27 19:29:19 +03:00

Author

Owner

@johncalvinyoung commented on GitHub (Dec 6, 2018):

It’s quite possibly a broken multicast implementation in your ISP router. I had a similar problem, and discovered that the otherwise-excellent router essentially could not forward multicast correctly (I think it WOULD work for IPv6 and not IPv4, but Spotify prefers the other, or something like that), and multicast -> zeroconf/avahi/Bonjour -> mDNS -> how librespot advertises itself on the network as an available speaker.

On Dec 6, 2018, at 6:50 AM, Alexandre Assouad notifications@github.com wrote:

Hello all,
I'm seeking guidance about a network issue.
I got a router hardware upgrade from my isp.
Since then I cannot connect.
My internal newtork has ipV6, I disabled it but it changed nothing

My questions:
Is there any debug mode for librespot ?
What tool could I use to debug this ?
Can it be a NAT traversal problem ?
Does spotify connect uses upnp ?

thanks for your insights

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/librespot-org/librespot/issues/278, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1dqAPkeL2sBJldXZDXTFnMEkcvd0BEks5u2QSegaJpZM4ZGWsk.

@johncalvinyoung commented on GitHub (Dec 6, 2018): It’s quite possibly a broken multicast implementation in your ISP router. I had a similar problem, and discovered that the otherwise-excellent router essentially could not forward multicast correctly (I think it WOULD work for IPv6 and not IPv4, but Spotify prefers the other, or something like that), and multicast -> zeroconf/avahi/Bonjour -> mDNS -> how librespot advertises itself on the network as an available speaker. > On Dec 6, 2018, at 6:50 AM, Alexandre Assouad <notifications@github.com> wrote: > > Hello all, > I'm seeking guidance about a network issue. > I got a router hardware upgrade from my isp. > Since then I cannot connect. > My internal newtork has ipV6, I disabled it but it changed nothing > > My questions: > Is there any debug mode for librespot ? > What tool could I use to debug this ? > Can it be a NAT traversal problem ? > Does spotify connect uses upnp ? > > thanks for your insights > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub <https://github.com/librespot-org/librespot/issues/278>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB1dqAPkeL2sBJldXZDXTFnMEkcvd0BEks5u2QSegaJpZM4ZGWsk>. >

kerem commented

2026-02-27 19:29:19 +03:00

Author

Owner

@t0k4rt commented on GitHub (Dec 6, 2018):

Thanks for your response,
Sorry but I forgot to mention that it appears correctly in my spotify connect devices.
The problem is that it refuses to connect on my internal network.
On my work network it works properly.
I can't see what could block
thanks again for your help !

@t0k4rt commented on GitHub (Dec 6, 2018): Thanks for your response, Sorry but I forgot to mention that it appears correctly in my spotify connect devices. The problem is that it refuses to connect on my internal network. On my work network it works properly. I can't see what could block thanks again for your help !

kerem commented

2026-02-27 19:29:19 +03:00

Author

Owner

@ashthespy commented on GitHub (Dec 6, 2018):

Logs are available by running librespot with the --verbose flag.
librespot uses the env_logger module to handle logs internally.
So RUST_LOG=mdns=trace ./librespot with your usual arguments will enable logs for the mdns module. Might help you figure out whats going on.

@ashthespy commented on GitHub (Dec 6, 2018): Logs are available by running `librespot` with the `--verbose` flag. `librespot` uses the [`env_logger`](https://docs.rs/env_logger/0.5.11/env_logger/#example) module to handle logs internally. So `RUST_LOG=mdns=trace ./librespot` with your usual arguments will enable logs for the `mdns` module. Might help you figure out whats going on.

kerem commented

2026-02-27 19:29:19 +03:00

Author

Owner

@t0k4rt commented on GitHub (Dec 6, 2018):

Thanks a lot,
I'll try this asap !

@t0k4rt commented on GitHub (Dec 6, 2018): Thanks a lot, I'll try this asap !

kerem commented

2026-02-27 19:29:19 +03:00

Author

Owner

@t0k4rt commented on GitHub (Dec 7, 2018):

Librespot seems to fail to connect to remote server.

Could my isp block this address ?

DEBUG:librespot_connect::discovery: Post "/" {}
INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-nxwj.ap.spotify.com:4070"
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 60, kind: TimedOut, message: "Operation timed out" }', libcore/result.rs:945:5
stack backtrace:
   0:        0x10ba8248b - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h4de839a9fdceed9d
   1:        0x10ba6c4ab - std::sys_common::backtrace::print::hc90998cb84923459
   2:        0x10ba7a6fd - std::panicking::default_hook::{{closure}}::ha08d7ed892ce8830
   3:        0x10ba7a45a - std::panicking::default_hook::hba629fe4bbe02041
   4:        0x10ba7ab76 - std::panicking::rust_panic_with_hook::h66872368c6c54afa
   5:        0x10ba7a9aa - std::panicking::begin_panic_fmt::hfc20a126d46a2dce
   6:        0x10ba7a8a2 - rust_begin_unwind
   7:        0x10bac2815 - core::panicking::panic_fmt::h6c19676a52234f8b
   8:        0x10b5ab1dd - core::result::unwrap_failed::h6d052e679d7ef1cb
   9:        0x10b59f72c - <librespot::Main as futures::future::Future>::poll::h2f251878ea24dddd
  10:        0x10b5a9687 - futures::task_impl::std::set::h879a82efa7b52dcd
  11:        0x10b5c0fe0 - <futures::future::lazy::Lazy<F, R> as futures::future::Future>::poll::hc4eb1e077223f156
  12:        0x10b5a9557 - futures::task_impl::std::set::h7ec98dbddaf5b36b
  13:        0x10b5ac342 - <std::thread::local::LocalKey<T>>::with::h2dabdb4f3952dafa
  14:        0x10b5bbef8 - <tokio::executor::current_thread::Entered<'a, P>>::block_on::h49cae2f91c216646
  15:        0x10b5ac7b8 - <std::thread::local::LocalKey<T>>::with::h889906fe6a21d74f
  16:        0x10b5ac1d7 - <std::thread::local::LocalKey<T>>::with::h08d610460b8bb16e
  17:        0x10b5ac4dd - <std::thread::local::LocalKey<T>>::with::h7dbec0ab18ef3d63
  18:        0x10b5b4165 - <scoped_tls::ScopedKey<T>>::set::hd8d41fa70ffd3da7
  19:        0x10b5bd063 - tokio_core::reactor::Core::run::h9eb020e5e6861a2a
  20:        0x10b5a1ac4 - librespot::main::h4dd0e77a6fcf3e14
  21:        0x10b5bd9b5 - std::rt::lang_start::{{closure}}::h4b69ab1b2dbd3b2b
  22:        0x10ba7a807 - std::panicking::try::do_call::hd1b51a136314709e
  23:        0x10ba9301e - __rust_maybe_catch_panic
  24:        0x10ba78a51 - std::rt::lang_start_internal::hb7855285a8133f7a
  25:        0x10b5a299b - main

@t0k4rt commented on GitHub (Dec 7, 2018): Librespot seems to fail to connect to remote server. Could my isp block this address ? ``` DEBUG:librespot_connect::discovery: Post "/" {} INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-nxwj.ap.spotify.com:4070" thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 60, kind: TimedOut, message: "Operation timed out" }', libcore/result.rs:945:5 stack backtrace: 0: 0x10ba8248b - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h4de839a9fdceed9d 1: 0x10ba6c4ab - std::sys_common::backtrace::print::hc90998cb84923459 2: 0x10ba7a6fd - std::panicking::default_hook::{{closure}}::ha08d7ed892ce8830 3: 0x10ba7a45a - std::panicking::default_hook::hba629fe4bbe02041 4: 0x10ba7ab76 - std::panicking::rust_panic_with_hook::h66872368c6c54afa 5: 0x10ba7a9aa - std::panicking::begin_panic_fmt::hfc20a126d46a2dce 6: 0x10ba7a8a2 - rust_begin_unwind 7: 0x10bac2815 - core::panicking::panic_fmt::h6c19676a52234f8b 8: 0x10b5ab1dd - core::result::unwrap_failed::h6d052e679d7ef1cb 9: 0x10b59f72c - <librespot::Main as futures::future::Future>::poll::h2f251878ea24dddd 10: 0x10b5a9687 - futures::task_impl::std::set::h879a82efa7b52dcd 11: 0x10b5c0fe0 - <futures::future::lazy::Lazy<F, R> as futures::future::Future>::poll::hc4eb1e077223f156 12: 0x10b5a9557 - futures::task_impl::std::set::h7ec98dbddaf5b36b 13: 0x10b5ac342 - <std::thread::local::LocalKey<T>>::with::h2dabdb4f3952dafa 14: 0x10b5bbef8 - <tokio::executor::current_thread::Entered<'a, P>>::block_on::h49cae2f91c216646 15: 0x10b5ac7b8 - <std::thread::local::LocalKey<T>>::with::h889906fe6a21d74f 16: 0x10b5ac1d7 - <std::thread::local::LocalKey<T>>::with::h08d610460b8bb16e 17: 0x10b5ac4dd - <std::thread::local::LocalKey<T>>::with::h7dbec0ab18ef3d63 18: 0x10b5b4165 - <scoped_tls::ScopedKey<T>>::set::hd8d41fa70ffd3da7 19: 0x10b5bd063 - tokio_core::reactor::Core::run::h9eb020e5e6861a2a 20: 0x10b5a1ac4 - librespot::main::h4dd0e77a6fcf3e14 21: 0x10b5bd9b5 - std::rt::lang_start::{{closure}}::h4b69ab1b2dbd3b2b 22: 0x10ba7a807 - std::panicking::try::do_call::hd1b51a136314709e 23: 0x10ba9301e - __rust_maybe_catch_panic 24: 0x10ba78a51 - std::rt::lang_start_internal::hb7855285a8133f7a 25: 0x10b5a299b - main ```

kerem commented

2026-02-27 19:29:19 +03:00

Author

Owner

@t0k4rt commented on GitHub (Dec 8, 2018):

Ok, I found the solution
It was related to my new isp router which was filtering all outbound connections by default.
Thanks for the help and sorry for the disturbance !

@t0k4rt commented on GitHub (Dec 8, 2018): Ok, I found the solution It was related to my new isp router which was filtering all outbound connections by default. Thanks for the help and sorry for the disturbance !

kerem referenced this issue

2026-02-27 20:00:06 +03:00

[PR #188] [MERGED] Add optional linear volume contol #828

Rows
Columns

[GH-ISSUE #278] Librespot connection issue #188