This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

HTML5 webm and ogg video not playing after upgrade to version 25

  • 1 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 6 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย jscher2000 - Support Volunteer

more options

Hi,

I have my video hosted on Amazon s3 and have the mime type set correctly to video/webm and video/ogg. I'm using the HTML 5 video tags which loads a mp4, webm or ogg video.

However after upgrading from Firefox 24 to 25 the video no longer loads, this is a problem specific to Firefox. The console just returns the message "All candidate resources failed to load. Media load paused."

You can find a link to the video here: http://taggled.tv/video/353

Any hints on where I'm going wrong? I've tried changing the mime type on the ogg video to application/ogg as someone recommended this, but still no luck!

Hi, I have my video hosted on Amazon s3 and have the mime type set correctly to video/webm and video/ogg. I'm using the HTML 5 video tags which loads a mp4, webm or ogg video. However after upgrading from Firefox 24 to 25 the video no longer loads, this is a problem specific to Firefox. The console just returns the message "All candidate resources failed to load. Media load paused." You can find a link to the video here: http://taggled.tv/video/353 Any hints on where I'm going wrong? I've tried changing the mime type on the ogg video to application/ogg as someone recommended this, but still no luck!

การตอบกลับทั้งหมด (1)

more options

Can you try it without adding the crossorigin attribute to the video tag? Since your server is not responding with an Access-Control-Allow-Origin header, I think this may be causing a silent cross-origin fail.