搭建MPEG-DASH服务器后视频无法播放，如何排查修复？

Looks like you're hitting a common DASH playback issue where individual segments work fine but the full stream won't load in dedicated players. Since your segments are accessible directly via Chrome, the problem is almost certainly tied to how your MPD file is structured or how Nginx is serving the DASH assets—not the segments themselves. Let's walk through the most likely fixes step by step:

1. Double-Check Segment Paths in Your MPD File #

First, verify that the MPD is pointing to the correct web-accessible paths for your segments, not local filesystem paths.

• Open your MPD file in a text editor. Look for <BaseURL> elements or the media attribute in <SegmentTemplate>/<SegmentList> tags.
• If all your files (MPD + segments) live in https://yourdomain/video/, the paths should be relative to the MPD's location. For example, instead of /wwwroot/default/video/segment_0.mp4, it should just be segment_0.mp4.
• Fix this by regenerating the MPD with MP4Box using relative paths. If your files are in the same directory, run:

  MP4Box -dash 2000 -frag 2000 -segment-name segment_$Number$ input.mp4 -out video.mpd
  

• Test the paths manually: When viewing the MPD in a browser, click the segment links to confirm they resolve to the correct files.

2. Ensure Nginx Serves the MPD with the Correct MIME Type #

DASH players require the MPD file to be served with the application/dash+xml MIME type. If Nginx is serving it as text/plain or another type, players will reject it.

• Add this to your Nginx server block (or update the mime.types file):

  types {
      application/dash+xml mpd;
  }
  

• Restart Nginx to apply changes:

  sudo systemctl restart nginx
  

• Verify the header: Use Chrome DevTools (Network tab) to check the Content-Type response header for your MPD—it should show application/dash+xml.

3. Enable CORS Headers in Nginx #

Most DASH players (like Akamai or DASH-IF Reference Player) run in browsers and require Cross-Origin Resource Sharing (CORS) headers to access assets, especially if the player is hosted on a different domain than your server.

• Add these headers to your Nginx location block for the video directory:

  location /video/ {
      add_header Access-Control-Allow-Origin *;
      add_header Access-Control-Allow-Methods GET, HEAD;
      add_header Access-Control-Allow-Headers Range;
  }
  

• For production, replace * with your player's specific domain instead of allowing all origins.
• Restart Nginx and test playback again.

4. Regenerate DASH Assets with Compatibility-Focused Parameters #

Even if segments play individually, incorrect timing or initialization data in the MPD can break playback. Regenerate your assets using standard, player-friendly parameters:
First, use FFmpeg to create a properly formatted MP4 (if you haven't already):

ffmpeg -i input.mp4 -c:v libx264 -crf 23 -c:a aac -b:a 128k -movflags +faststart output.mp4

Then run MP4Box to generate DASH segments and MPD with random access points (required for smooth playback):

MP4Box -dash 2000 -rap -frag-rap -segment-name segment_ output.mp4 -out video.mpd

5. Check for MPD Syntax/Codec Mismatches #

• Use ffprobe to verify the codecs in your segments match what's declared in the MPD:

  ffprobe segment_0.mp4
  

  Ensure the MPD's codecs attribute in <Representation> tags matches the output (e.g., avc1.64001E,mp4a.40.2).
• Look for missing initialization segments: The MPD should reference an init.mp4 (or similar) file—confirm this file exists and is accessible.

If you're still stuck, check the browser's DevTools Console for error messages. Players often log specific issues like missing CORS headers or invalid MPD syntax there, which can point you directly to the problem.

内容的提问来源于stack exchange，提问作者renkang chen