Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

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!

Alle antwoorden (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.