ZEE5 Broken Site ( HTTP Error 400: Bad Request )
See original GitHub issueChecklist
- I’m reporting a broken site
- I’ve verified that I’m running yt-dlp version 2022.03.08.1. (update instructions)
- I’ve checked that all provided URLs are alive and playable in a browser
- I’ve checked that all URLs and arguments with special characters are properly quoted or escaped
- I’ve searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
- I’ve read the guidelines for opening an issue
- I’ve read about sharing account credentials and I’m willing to share it if required
Region
No response
Description
Unable to download a lot of URLs from ZEE5, I have confirmed they are playable on non-DRM Browsers.
Verbose log
[debug] Command-line config: ['https://www.zee5.com/kids/kids-shows/indias-best-dramebaaz-2018/0-6-tvshow_225807515/indias-best-dramebaaz-2018/0-1-tvshow_225807515-season_1636655307-episode_1767761271', '--verbose', '-o', 'Downloads/%(title)s.%(ext)s', '--cookies-from-browser', 'chrome', '-N', '20']
[Cookies] Extracting cookies from chrome
[debug] Extracting cookies from: "/Users/dd/Library/Application Support/Google/Chrome/Default/Cookies"
[debug] using find-generic-password to obtain password from OSX keychain
[Cookies] Extracted 3274 cookies from chrome
[debug] cookie version breakdown: {'v10': 3207, 'other': 0, 'unencrypted': 67}
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, err utf-8, pref UTF-8
[debug] yt-dlp version 2022.03.08.1 [c0c2c57d3] (zip)
[debug] Lazy loading extractors is disabled
[debug] Python version 3.9.10 (CPython 64bit) - macOS-12.1-arm64-arm-64bit
[debug] exe versions: ffmpeg 5.0 (setts), ffprobe 5.0, rtmpdump 2.4
[debug] Optional libraries: Cryptodome, sqlite
[debug] Proxy map: {}
[debug] Using fake IP 117.254.45.16 (IN) as X-Forwarded-For
[debug] [Zee5] Extracting URL: https://www.zee5.com/kids/kids-shows/indias-best-dramebaaz-2018/0-6-tvshow_225807515/indias-best-dramebaaz-2018/0-1-tvshow_225807515-season_1636655307-episode_1767761271
[Zee5] 0-1-tvshow_225807515-season_1636655307-episode_1767761271: Downloading access token
[Zee5] 0-1-tvshow_225807515-season_1636655307-episode_1767761271: Downloading JSON metadata
ERROR: [Zee5] 0-1-tvshow_225807515-season_1636655307-episode_1767761271: Unable to download JSON metadata: HTTP Error 400: Bad Request (caused by <HTTPError 400: 'Bad Request'>); please report this issue on https://github.com/yt-dlp/yt-dlp , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 617, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/yt-dlp/yt_dlp/extractor/zee5.py", line 136, in _real_extract
json_data = self._download_json(
File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 997, in _download_json
res = self._download_json_handle(
File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 976, in _download_json_handle
res = self._download_webpage_handle(
File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 768, in _download_webpage_handle
urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal, data=data, headers=headers, query=query, expected_status=expected_status)
File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 753, in _request_webpage
raise ExtractorError(errmsg, cause=err)
File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 735, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/yt-dlp/yt_dlp/YoutubeDL.py", line 3589, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/opt/homebrew/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 523, in open
response = meth(req, response)
File "/opt/homebrew/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 632, in http_response
response = self.parent.error(
File "/opt/homebrew/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 561, in error
return self._call_chain(*args)
File "/opt/homebrew/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/opt/homebrew/Cellar/python@3.9/3.9.10/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.py", line 641, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 400: Bad Request
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:10 (3 by maintainers)
Top Results From Across the Web
How to Fix a 400 Bad Request Error [Causes and Fixes]
The HTTP error 400 can be caused by the file you're uploading being too large. That's usually because there's a file size limit...
Read more >The error appears when I play any Premium video
The error appears when I play any Premium video ... Update the ZEE5 App (Click here to know how). ... Clear the web...
Read more >8 Easy Ways to Fix HTTP Error 400 Bad Request - Apeaksoft
The HTTP 400 bad request error can be caused by a malware infection. As a result, your computer may be corrupted or damaged...
Read more >Error 400 Bad Request when I click "Edit Project"
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible....
Read more >Why is Tubi TV not working? - Quora
Update the Widevine Content Decryption Module · Ensure to give Widevine Content Decryption Module full access · Reinstall Chrome · Check your antivirus...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kr-v Stop @ ing repeatedly. If someone is willing to work on the issue, and wants to ask for account details, they will
How to fix this issue, again?
Is there a procedure to find the
_DEVICE_ID
and_DETAIL_API_URL
I think it is discovered by observing calls to
spapi.zee5.com
(when loading the page) in the console