Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

"Media Could Not Be Played" on Tweetdeck.

  • 2 відповіді
  • 3 мають цю проблему
  • 1 перегляд
  • Остання відповідь від dualirium

more options

Hello. I'm having this issue recently in Tweetdeck on Firefox. When i clic on a video it loads but then shows "Media Could Not Be Played". It plays well on Twitter.com and other browsers like Chrome. It also worked fine the first days of the Firefox Quantum update. The videos among others websites like Facebook and YouTube are ok, no problem at all. The images and gifs works fine also.

Here's what i've already tried:

- Restart with Addons disabled. - Check Plugins - Check Flash and Java. - Check permissions on site. - Update Tweetdeck.

Can't seem to find a solution neither on the forum or somewhere else.

Thanks in advance.

Hello. I'm having this issue recently in Tweetdeck on Firefox. When i clic on a video it loads but then shows "Media Could Not Be Played". It plays well on Twitter.com and other browsers like Chrome. It also worked fine the first days of the Firefox Quantum update. The videos among others websites like Facebook and YouTube are ok, no problem at all. The images and gifs works fine also. Here's what i've already tried: - Restart with Addons disabled. - Check Plugins - Check Flash and Java. - Check permissions on site. - Update Tweetdeck. Can't seem to find a solution neither on the forum or somewhere else. Thanks in advance.

Усі відповіді (2)

more options

Could be a CSP issue. You can check the Web Console (Tools -> Web Developer) for messages about blocked content.

See also:

more options

Hi Cor-El. Thanks a lot for your help. I'm checking your suggestions and still trying to figure out this issue. In the Web Console there´s this error messages:

XML Parsing Error: no root element found Location: https://tweetdeck.twitter.com/metrics Line Number 1, Column 1: metrics:1:1 (This ones repeats a few times) Invalid URI. Load of media resource failed. Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive. Content Security Policy: Directive ‘frame-src’ has been deprecated. Please use directive ‘child-src’ instead. Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src 'unsafe-eval' https://twitter.com http://localhost:* http://localhost.twitter.com:* https://*.twitter.com https://*.twimg.com https://vine.co https://*.vine.co https://*.periscope.tv https://*.pscp.tv”). Source: onfocusin attribute on DIV element. 948681161039011840 Content Security Policy: The page’s settings blocked the loading of a resource at blob:https://twitter.com/74c2d0d1-cf3d-4dfe-b93b-bfcdaec1b7e4 (“default-src https://twitter.com http://localhost:* http://localhost.twitter.com:* https://*.twitter.com https://*.twimg.com https://vine.co https://*.vine.co https://*.periscope.tv https://*.pscp.tv”).

I'm not sure what it means but i think i have an idea, the last ones shows the video being blocked. I did a clean reinstall of Firefox, there's no account linked nor addons installed. I'm also checking the second link you posted and the guy in there happen to mention the CSP message about the loading of the resource being blocked. Your last suggestion was to contact Twitter but i'm not sure if the problem is on their end. I forgot to mention something in my question. There's some websites where the videos from certain sources simply don't appear. For example, a website here in México post an article, mention that there's a video and the only thing visibly is a link. It happens with Facebook and Twitter videos, but not with videos form YouTube. This last issue happens also on Chrome but not on Edge. I'm not sure if is related but maybe has something to do with the Tweetdeck problem.