Short answer

Safari supports HLS natively. Chrome often needs hls.js and stricter JavaScript fetch conditions. CORS, codec support and segment access can make the same URL behave differently.

What to check

  • Confirm that the stream is public or authorized for testing.
  • Use the Checker to separate access problems from playlist structure.
  • Do not treat a diagnostic result as permission to copy, bypass or redistribute media.

Next step

If the answer points to access, fix the origin policy or authorization first. If access works, continue with playback, segment and codec checks.