Closed BerendWouters closed 3 weeks ago
Does this issue still occur using the edge
container? There was a fix for https://github.com/advplyr/audiobookshelf/issues/3246, not sure if it's the same thing.
I just ran it with the latest
tag locally, and it seems to be working. Which is odd, because it's the same digest as being used by the actual server running it.
Going to try edge
on the actual server now.
Sadly enough, no changes running it on the edge
version either. Might be a docker networking related issue, unsure.
Downloading other episodes works just fine.
I tested and I'm not able to reproduce the issue. Are you still able to reproduce it? If it is reproducible still, is there specific episodes it happens with? Any other podcasts?
The issue still occurs with any episode of The WAN Show
This is most likely a network issue since it is timing out. Having a 30 second timeout seems reasonable
It was a networking issue indeed. My docker/daemon.json
also had the ip address of the docker server itself, which the internal networking didn't like. It's working now.
What happened?
I'm attempting to download an episode from the WAN Show, using the following link: https://pdst.fm/e/chrt.fm/track/C76EG6/mgln.ai/e/94/claritaspod.com/measure/verifi.podscribe.com/rss/p/chtbl.com/track/289382/pfx.vpixl.com/j0JIg/traffic.megaphone.fm/ROOSTER8312874402.mp3?updated=1722970170 This link is redirecting through multiple tracking websites, and ending up at the https://pfx.vpixl.com/j0JIg/traffic.megaphone.fm/ROOSTER8312874402.mp3?updated=1722970170 url, which seems to timeout. However, if I run this in a browser, it works just fine.
It also occurs with other episodes
What did you expect to happen?
The episode being downloaded
Steps to reproduce the issue
Audiobookshelf version
2.12.1
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
I've tried recreating the request in Postman, and I get a
Maximum response size reached
, but that might be related to Postman not being able to process the download.