[GH-ISSUE #92] Download Failed Errors #77

Closed
opened 2026-03-03 00:07:36 +03:00 by kerem · 1 comment
Owner

Originally created by @PercBirdie on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/binimum/tidal-ui/issues/92

When downloading and exporting to ZIP Archive, error text file is included in ZIP file:

"Error: Download failed. The stream URL may require a proxy. Please try streaming instead."

This happens with songs being downloaded individually but comes up as a error bubble with same message on UI client.

Error occurs when trying to stream songs as well.

Songs that successfully download seem to be random, as a second try might yield songs that wouldn't download before. This issue began to occur about 5 days ago.

Tested on:
Fedora Linux 43, MacOS Tahoe 26.1, & Android 16
Firefox and Chrome browsers
Two seperate networks

Occurs on self hosted and on https://music.binimum.org/

Originally created by @PercBirdie on GitHub (Jan 6, 2026). Original GitHub issue: https://github.com/binimum/tidal-ui/issues/92 When downloading and exporting to ZIP Archive, error text file is included in ZIP file: "Error: Download failed. The stream URL may require a proxy. Please try streaming instead." This happens with songs being downloaded individually but comes up as a error bubble with same message on UI client. Error occurs when trying to stream songs as well. Songs that successfully download seem to be random, as a second try might yield songs that wouldn't download before. This issue began to occur about 5 days ago. Tested on: Fedora Linux 43, MacOS Tahoe 26.1, & Android 16 Firefox and Chrome browsers Two seperate networks Occurs on self hosted and on https://music.binimum.org/
kerem 2026-03-03 00:07:36 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@binimum commented on GitHub (Jan 6, 2026):

This error is really badly written and is from the start of the project, when I used a CORS proxy. This basically means that all APIs failed to return a response - usually trying again a few times does the trick. If you are listening to an Atmos version of a track then this error will also occur due to some APIs using non-Atmos accounts.

<!-- gh-comment-id:3716505605 --> @binimum commented on GitHub (Jan 6, 2026): This error is really badly written and is from the start of the project, when I used a CORS proxy. This basically means that all APIs failed to return a response - usually trying again a few times does the trick. If you are listening to an Atmos version of a track then this error will also occur due to some APIs using non-Atmos accounts.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tidal-ui#77
No description provided.