Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Viki with an account. Getting a 403 : Forbidden (caused by HTTPError()) when downloading on Windows 10. #24754
Comments
|
I can confirm this issue exist, and is definitely a very recent one, this issue did not exist on 12th Apr local time. |
|
Try increase the --socket-timeout, in my case i set it to 10 seconds and works again. |
|
I have the exact same issue on Mac OS. Since this morning, trying to download Viki Pass HD videos results in a 403 forbidden error. I am a Viki Pass subscriber with a valid account. Downloading standard definition videos without a login on Viki still works, but the HD video downloads for Viki Pass subscribers are no longer working. The suggested fix of increasing the --socket-timeout did NOT work for me. |
|
same problem here as at 15th april.Any solution? |
|
I'm getting the feeling that this is not a problem of youtube-dl, but a new limit implemented by youtube/google themselves |
Yess!!! 30seconds for me |
|
Trying to download using the cookies.txt workaround gives a 401 error instead of a 403; maybe this will be helpful in determining the cause of the error. --socket-timeout did not work with the cookies workaround or authentication through the arguments. I used cookies.txt for Chrome and exported the cookies from a tab playing an episode.
|
Still doesn't work, can you post the command you input? |
Doesn't work for me. Can you post the command? |
Checklist
Verbose log
Description
Hopefully I have created this issue properly. So basically when streaming through the browser I am getting 1080p HD quality for this video, but when going to youtube-dl to download them, I am getting the issues given above. I have posted two logs with two different cases. I have run the --cookies command instead of the username and password, and that doesn't seem to work also.
If an account is needed I can give the account to the dev to reproduce and check the problem for a fix. I am on Windows 10 if that is relevant anyhow. If there are anymore details required, please let me know and I'll provide them too.
Thank you.