-
Notifications
You must be signed in to change notification settings - Fork 40
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
WinError 2 when trying to run #86
Comments
Hello @dougyp, thank you for your interest in our work! If this is a bug report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you. |
The cause of the error is that the
In addition, downloading a single video via ffmpeg does not require cookies, so this is not a problem. |
@lonsty perfect - that was the problem and worked fine! sorry to report it "as a bug" but I didn't see where I can ask "support" questions. thank you for your time. |
🐛 Bug Report
I am running on a Windows 10 machine with gitbash. I installed the software and no errors during installation. When I run it, it never did ask for the cookie (first problem)
But when I try to run it for any URL at xvideos it gives the video name, video page, resolution, etc. and then an error. Here is the output with one random sample:
$ xvideos-dl https://www.xvideos.com/video65461739/madison_summers_step_brother_cums_in_his_pants
Downloading: ⚓
Video ID : 65461739
Video Name : Madison Summers Step Brother Cums In His Pants
Video Page : https://www.xvideos.com/video65461739/_
Resolution : 720p @ 1280x720
Destination: C:\Users\doug\Downloads\xvideos\Madison Summers Step Brother Cums
In His Pants(#65461739).mp4
[WinError 2] The system cannot find the file specified
🔬 How To Reproduce
Steps to reproduce the behavior:
Code sample
Environment
Screenshots
📈 Expected behavior
I hoped it would create a file. It does create ./xvideos folder.
📎 Additional context
When I ran it, it never asked for the cookie like the instructions said it would. I did finally create a file ~/.xvideo/cookie and pasted "session_token=". But that made no difference.
The text was updated successfully, but these errors were encountered: