-
Notifications
You must be signed in to change notification settings - Fork 508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Cookies don't seem to work when queuing download via the web frontend? Why are the working on the command line? Are they really passed to yt-dlp? #564
Comments
debug log
I can download this video with webui but cookies. I think it has nothing to do with cookies and should check for network (connectivity, dns, ipv6?) issues |
So I See that you have set impersonate in your options file. I don't have this and running
inside the container shows me, that no targets are available. So I can't use impersonate targets. I know both commands above complains:
BUT, this is running with yt-dlp on the command line inside of the container. So the missing impersonate targets should not be an issue. I also don't think there are any networking issues as everything works fine (e.g. download other freely available videos from Vimeo). If you want to retest it, please use the below URL for download. That was my actual problematic movie, the other one was just from some additional testing (which also didn't work, but which I also didn't purchased): |
can you test it with yt-dlp command line? |
Okay, interesting... If I just use "yt-dlp https://vimeo.com/ondemand/heimreise/388045885" without any additional parameters (so no cookies):
It is just downloading 1.8MB and the resulting video is the Trailer of the on-demand video. However, if I provide the cookie file which ontains my login-session - "yt-dlp --cookies /cookies/cookies.txt https://vimeo.com/ondemand/heimreise/388045885". The same link will download the full video (see the downloaded size):
So it definitely makes a difference and take the cookie data which is not happening when I queue the link via the web frontend. But I overall I spent some more time on investigating the issues. From your log file I could see that you have provided the impersonate option. So while I was able to install the "curl_cffi" on top of the docker container, I'm having trouble to provide the correct impersonate parameters. So could you please let me know how you have defined them in your YTLD_OPTIONS? Maybe this helps to solve the issue. |
Okay, I found a quick work-around: I simply added the Vimeo username and password to my YT_DLP_OPTIONS file. I know, this is totally insecure, but due to the fact that I am the only one having access to this server, I can deal with it. I still think there is something broken, but as I seems to be the only one having this issue, I don't want to waste anybody's time anymore. |
Okay, so I want to download an on demand video from Vimeo. I do have the cookies of my account saved to a txt file and adjusted the YTDL_OPTIONS_FILE file to contain:
"cookiefile": "/cookies/cookies.txt",
But if I queue the download via the web interface, the download fails with "No video formats found!" which is normal when you are not authorised. So here is the log:
I first thought, the cookies are expired. However, I did another test and logged into the container and running yt-dlp from the shell. Which works completely fine and download the video.
Soooo, the big question: So why is this working on the command line? How can I make this work? Is the app really passing the cookie file to yt-dlp when downloading a video?
The text was updated successfully, but these errors were encountered: