No announcement yet.

Tidal issue, Connect Reset By Local Host

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tidal issue, Connect Reset By Local Host

    My neighbor is operating a 2.4 Vortexbox that I built for him with LMS and Plex running on it. Running Logitech Media Server Version: 7.9.1 - 0.4.20170705git1498799744 @ Tue Aug 1 18:35:55 EDT 2017. He has Tidal installed, an active subscription, and has been using Tidal via the App Icon on his Squeezebox Touch for over a year. Now for the problem. On Wednesday he built a playlist using Tidal files adding them to the Touch. Tidal found the music, placed the tracks in order on the Touch, he pressed Play and the Touch showed about 8 to 10 seconds moving on the song time line but without any audio output, then Touch displayed "Connection Reset By Local Host", then moved to the next song in the playlist to repeat the exact same event over and over until reaching a song in the playlist that was from his ripped files which played. So he called and asked if I had time to drop by and have a look.

    I have powered down and rebooted his router, modem, servers, and Squeezeboxen. It is still doing the exact same thing. I searched 5 different streaming forums and Googled this error with the one suggestion being it is a firewall issue or privilege setting. Well that doesn't make sense because it's been working over a year and nothing has been changed (on Router, Modem, or Firewall) PLUS he can stream Tidal on his phone, laptop, and PCs (via WiFi and Ethernet) which are all having to get that data stream through said Internet connection, Router, Firewall. I found a Post on the Slim Devices forum from the last week in April that stated only US users were unable to stream Tidal on Squeezebox but that it had since been mostly resolved. That isn't the case here or we are dealing with an additional/new issue now.

    Has anybody else seen this problem? Thoughts, suggestions, things to look at, things to try?

  • #2
    Similar problems here with Tidal & Radio Paradise, usually after rebooting the Vortexbox. The workaround I've been using is to uninstall the plugins, allow LMS to restart, then reinstall the plugins and allow LMS to restart again.