If you see web_4000 or Shaka error 4000, it means the player cannot detect the manifest type of your stream URL. Error code 4000 (UNABLE_TO_GUESS_MANIFEST_TYPE) occurs when the player fails to identify whether the source is a valid DASH or HLS stream based on the URL or server response.
This issue often appears when the stream URL is wrong, the server sends the wrong content type, the URL redirects to something unexpected, or the manifest request returns an HTML page instead of a real streaming file. This error is mainly triggered when the file extension or response type does not clearly indicate the stream format.
What Causes web_4000 Shaka Error 4000
Shaka Player expects a playable manifest such as:
- DASH manifest ending in .mpd
- HLS manifest ending in .m3u8
If the URL does not clearly identify the format, Shaka tries to detect it from the server response. If that also fails, it throws error 4000. This error occurs when the player cannot detect the stream format from the URL or server response.
How to Fix web_4000 Shaka Error 4000
Use the steps below to troubleshoot and fix the error.
Step 1: Check the stream URL
Start by looking at the URL you pass into player.load().
A proper manifest URL should normally look like this:
player.load('https://example.com/stream.mpd');or
player.load('https://example.com/playlist.m3u8');If your URL ends in something like:
/watch?id=123/video/manifest.php/play/stream?token=abc
then Shaka may not know what it is unless the server sends a very clear manifest MIME type. Always use a recognizable file extension whenever possible.
Step 2: Open the manifest URL directly in the browser
Paste the URL into your browser.
Now check what opens:
- If you see a text manifest, that is a good sign
- If you see a login page, error page, or HTML site, that is the problem
- If the file downloads strangely or shows an access error, the URL is likely invalid or blocked
If the source is protected, your player may be requesting a page that only works in a logged-in browser session, not in the video player request flow.
Step 3: Inspect the response headers in DevTools
Open Developer Tools in your browser and check the Network tab.
Look at the manifest request and inspect:
- Status code
- Final URL after redirect
- Content-Type
- Response body
For DASH, the response should normally identify as application/dash+xml. Shaka issue discussions also show that incorrect or unexpected content types can trigger error 4000.
If you see text/html, the request is likely hitting:
- a login page
- an error page
- a CDN block page
- a 403 or 404 HTML response
- a failed token endpoint
That means Shaka is not receiving a real manifest.
Step 4: Make sure the server allows HEAD requests
Shaka’s own error explanation lists HEAD request support as one of the things that can help the player detect manifest type correctly. Make sure your server accepts HEAD requests for the manifest, or detection may fail.
If your server blocks HEAD requests with 405 Method Not Allowed, detection can fail.
Step 5: Fix redirects
If your URL redirects before reaching the final media source, inspect the full redirect chain.
Problems often happen when:
- the first URL is generic
- the final file type changes unexpectedly
- authentication breaks during redirect
- the redirect lands on a non-manifest page
Shaka users have reported error 4000 in redirect-based playback setups, especially when the original URL hides the true media resource.
The safest fix is simple: use the final direct manifest URL instead of the redirecting URL.
Step 6: Confirm you are loading a supported stream type
Shaka works best with DASH and HLS. If you try to load a source that is not a standard Shaka manifest, the player may fail before playback starts. Non-standard formats will not load unless a proper parser plugin is configured.
If your source is custom, you may need:
- a manifest parser plugin
- a direct supported manifest file
- a different playback approach for non-manifest media
Step 7: Test with a known working manifest
Before changing your whole setup, test Shaka with a known-good manifest. If the test stream works, your player setup is fine and the issue is almost certainly with your URL, headers, or backend response.
This helps you quickly separate:
- player-side problem
- server-side problem
Example of a Broken Setup
Here is a typical setup that causes error 4000:
player.load('https://example.com/play?id=92837');Why this fails:
- the URL does not end in
.mpdor.m3u8 - the backend may return
text/html - the request may redirect to a protected page
- the player cannot guess the manifest type
Example of a Better Setup
player.load('https://cdn.example.com/live/channel1/manifest.mpd');Why this works better:
- the URL clearly ends in
.mpd - the format is obvious
- the player can identify the manifest faster
- fewer redirects reduce failure points
To fix web_4000 Shaka error 4000, make sure your player loads a real DASH or HLS manifest, not a generic endpoint or HTML page. The most reliable fix is to use a direct .mpd or .m3u8 manifest URL, return the correct response headers, and remove broken redirects or invalid backend responses.
