Closed tvillini closed 1 year ago
Hmm, maybe the url / connection to your friends media server could have changed in the mean time. Did you try to sync and try to download your friend's media right after?
I did. I can try again, but I even tried wiping the database, and starting a fresh docker container just to make sure.
On Oct 5, 2023, at 1:23 PM, Felix Steinfurth @.***> wrote:
Hmm, maybe the url / connection to your friends media server could have changed in the mean time. Did you try to sync and try to download your friend's media right after?
— Reply to this email directly, view it on GitHub https://github.com/fxsth/pledo/issues/16#issuecomment-1749347772, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGZWRS2QLNUPTR5Q6UMDPWLX53UJ3AVCNFSM6AAAAAA5P6L4FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGM2DONZXGI. You are receiving this because you authored the thread.
I figured out that a download request on some connection uris (namely 'plex.direct'-Uris) return a bad request response, even when syncing with this uri is totally fine. So the downloader is now considerung direct connections with http uris and even trying different ones when the selected one is not working. You can try out the latest release 1.3.0, I'm hopeful that it will fix your problem.
Same issue.

However the direct download DOES work. Also, the logging shows more stuff on the regular download: 
Thanks!
On Oct 21, 2023, at 6:23 AM, Felix Steinfurth @.***> wrote:
I figured out that a download request on some connection uris (namely 'plex.direct'-Uris) return a bad request response, even when syncing with this uri is totally fine. So the downloader is now considerung direct connections with http uris and even trying different ones when the selected one is not working. You can try out the latest release 1.3.0, I'm hopeful that it will fix your problem.
— Reply to this email directly, view it on GitHub https://github.com/fxsth/pledo/issues/16#issuecomment-1773744929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGZWRS4YEORG4Y5DKWDJFGLYAOPCNAVCNFSM6AAAAAA5P6L4FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTG42DIOJSHE. You are receiving this because you authored the thread.
Unfortunately the send attachments like logs in your comment are not readable...
Thanks, that is helping. Seems that there is an issue with the created filename that is derived from original filename at the source media server. Linux and Windows directory seperator are mixed up, when running pledo on linux and the plex media server on windows: '/media/Y:\Movies\BlackBerry (2023).mkv'. Will be fixed right away.
Fixed on 1.3.1
Thank you, that worked!!
On Oct 21, 2023, at 11:42 AM, Felix Steinfurth @.***> wrote:
Fixed on 1.3.1
— Reply to this email directly, view it on GitHub https://github.com/fxsth/pledo/issues/16#issuecomment-1773834478, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGZWRSZPQ64UUPU7COCI3ZTYAPUNNAVCNFSM6AAAAAA5P6L4FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTHAZTINBXHA. You are receiving this because you authored the thread.
When I try to download from a friend's library, it shows as cancelled immediately. I'm not really sure what the issue is, and don't really know where to find the logs to triage the issue. I thought for a bit it might be an issue of rights to the storage, but I attached to the docker container and was able to see the storage mounted and writable. I also DID try to download from my own library, and that was successful. It's just an issue from a friend's library. Thanks for any help!