Offline file download continues well past actual file size

Support
1

Issue description:

Hello! First of all I want to say a big thanks for building such a flexible and easy to use app, its audiobook support far outstrips Plexamp’s and I love being able to tweak it just how I like.

I’ve been having an issue recently whereby when I try to create an offline backup of one of my audiobooks, the download manager just continues endlessly, way past the original file size. I’ve tried getting the exact same file through Plexamp and that seems to work without issue, so I’m wondering if it could be something on the Symfonium side. Logs should hopefully be uploaded - any help will be hugely appreciated!

Logs:

Upload description: asongtoruin_202531

Additional information:

 
Attached screenshot is for a 200mb-ish file
 

Reproduction steps:

 

 

Media provider:

Plex

Screenshots:

 

Screenshot 1
Screenshot 11079×1210 193 KB
    

2

The logs does not show the start of the download so hard to tell, but your server is happily sending the data that Symfonium store as received.

Something happens on server side.

3

Apologies, I thought I’d activated debug mode before the download started. I’ve just retried and reuploaded the logs (description “asongtoruin_20251231_2”).

4

Hum you are connected via PlexRelays that enforce a BW limit, and Plex for unknown reasons force transcode to MP3 despite the media being under the limit and then generate a bad mp3.

Lot of strange stuff on Plex side here :frowning:

Do you think you can send me an invite to the server to support at symfonium dot app for just that file so I can try to reproduce and find a workaround ?

5

Well, that’s given me something to investigate.

I’ve tried completely disabling Plex Relays on the server side and reinstalled Symfonium, and now Symfonium refuses to connect to my server when I’m on the same network (Plexamp and web-based Plex seem to connect without issue). I’ve added the logs for this (description “asongtoruin_20260101”).

Having a quick scan through those logs, in line 119 and 150, I clocked there’s some plex.direct URLs rather than just the raw (public or private) IP address. A quick googling suggested it could be a DNS issue - as I’m on Android, I tried changing the “Private DNS” setting to one of the standard ones. Surprisingly, that seems to have worked. So, some debugging

  1. If I then change the DNS setting back to “Auto”, trying to access any of my files seems to give a “Not connected to Wi-Fi” error message. Changing back to “Private DNS” again lets the file download without issue.
  2. I’ve then tried re-enabling Plex Relays on the server (while still having the “Private DNS” set), and the downloads seem fine.

My best guess here is that if the DNS lookup fails it’s automatically falling back to the relays, where something weird is happening.

But I have a fix for now! I’ll keep an eye to see if this keeps going without issue. Many thanks :smile:

6

Those urls are returned by Plex and are necessary to have secured https connection.

All DNS should be able to resolve them/