[GH-ISSUE #149] Repeated connection failure #91

New issue

Closed

opened 2026-02-28 14:25:16 +03:00 by kerem · 1 comment

kerem commented

2026-02-28 14:25:16 +03:00

Owner

Originally created by @linknum23 on GitHub (Nov 21, 2024).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/149

One of AmpliPi's customers appears to be having this issue with go-librespot_linux_armv6_rpi.tar.gz running on a Pi3 compute module with a log that looks similar to an older solved issue; #88

time="2024-11-19T17:31:24-07:00" level=info msg="running go-librespot 0.1.2"
time="2024-11-19T17:31:24-07:00" level=info msg="generated new device id: 4907a0325a22d241f6dbc510fe718603dad8c512"
time="2024-11-19T17:31:24-07:00" level=info msg="api server listening on 127.0.0.1:3679"
time="2024-11-19T17:31:37-07:00" level=info msg="zeroconf server listening on port 39801"
time="2024-11-19T17:41:10-07:00" level=warning msg="failed to connect to AP ap-guc3.spotify.com:4070, retrying with a different AP" error="dial tcp 104.154.127.247:4070: connect: connection refused"
time="2024-11-19T17:41:10-07:00" level=info msg="authenticated AP as matchmee"
time="2024-11-19T17:41:11-07:00" level=info msg="authenticated Login5 as matchmee"
time="2024-11-19T17:41:11-07:00" level=info msg="accepted zeroconf user matchmee from iPhone"
time="2024-11-19T17:42:41-07:00" level=error msg="did not receive last pong from dealer, 60s passed"
time="2024-11-19T17:43:11-07:00" level=error msg="did not receive last pong from dealer, 90s passed"
time="2024-11-19T17:43:41-07:00" level=error msg="did not receive last pong from dealer, 120s passed"
time="2024-11-19T17:44:11-07:00" level=error msg="did not receive last pong from dealer, 150s passed"
time="2024-11-19T17:44:41-07:00" level=error msg="did not receive last pong from dealer, 180s passed"
time="2024-11-19T17:45:11-07:00" level=error msg="did not receive last pong from dealer, 210s passed"
time="2024-11-19T17:45:41-07:00" level=error msg="did not receive last pong from dealer, 240s passed"

I will see if I can get the relevant stack traces from the customers unit with a SIGABRT as we have not been able to reproduce this internally.

Originally created by @linknum23 on GitHub (Nov 21, 2024). Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/149 One of AmpliPi's customers appears to be having this issue with go-librespot_linux_armv6_rpi.tar.gz running on a Pi3 compute module with a log that looks similar to an older solved issue; #88 ``` time="2024-11-19T17:31:24-07:00" level=info msg="running go-librespot 0.1.2" time="2024-11-19T17:31:24-07:00" level=info msg="generated new device id: 4907a0325a22d241f6dbc510fe718603dad8c512" time="2024-11-19T17:31:24-07:00" level=info msg="api server listening on 127.0.0.1:3679" time="2024-11-19T17:31:37-07:00" level=info msg="zeroconf server listening on port 39801" time="2024-11-19T17:41:10-07:00" level=warning msg="failed to connect to AP ap-guc3.spotify.com:4070, retrying with a different AP" error="dial tcp 104.154.127.247:4070: connect: connection refused" time="2024-11-19T17:41:10-07:00" level=info msg="authenticated AP as matchmee" time="2024-11-19T17:41:11-07:00" level=info msg="authenticated Login5 as matchmee" time="2024-11-19T17:41:11-07:00" level=info msg="accepted zeroconf user matchmee from iPhone" time="2024-11-19T17:42:41-07:00" level=error msg="did not receive last pong from dealer, 60s passed" time="2024-11-19T17:43:11-07:00" level=error msg="did not receive last pong from dealer, 90s passed" time="2024-11-19T17:43:41-07:00" level=error msg="did not receive last pong from dealer, 120s passed" time="2024-11-19T17:44:11-07:00" level=error msg="did not receive last pong from dealer, 150s passed" time="2024-11-19T17:44:41-07:00" level=error msg="did not receive last pong from dealer, 180s passed" time="2024-11-19T17:45:11-07:00" level=error msg="did not receive last pong from dealer, 210s passed" time="2024-11-19T17:45:41-07:00" level=error msg="did not receive last pong from dealer, 240s passed" ``` I will see if I can get the relevant stack traces from the customers unit with a SIGABRT as we have not been able to reproduce this internally.

kerem

2026-02-28 14:25:16 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-28 14:25:17 +03:00

Author

Owner

@linknum23 commented on GitHub (Dec 5, 2024):

The user that reported this realized that their Spotify connection was blocked by a firewall rule. I think it is safe to close this.

@linknum23 commented on GitHub (Dec 5, 2024): The user that reported this realized that their Spotify connection was blocked by a firewall rule. I think it is safe to close this.

kerem referenced this issue

2026-02-28 14:26:14 +03:00

[PR #91] [MERGED] fix: small fixes to accesspoint connect retry logic #202