Firefox is not playing Instagram stories

Hi

When playing Instagram stories [videos], I can only hear the audio since I updated to version 14.7.0 Mega. I can only see the frozen picture of the video with the audio.

So far this only happens with the stories on Instagaram.

Also, I update the flash using the link that you have at the home screen of the site.

I'm using Windows 7 with Firefox 65.0.2 (64-bit)

I don't know why this happens, it's the only wrong thing.

I also need to say that I try using the Firefox with all the addons and extensions disabled, and it happens the same thing.

I don't know if this is linked to the problem, but I have an AOL email account and it gets stuck on the "loading" bar and I never access to the home screen of my email on AOL, but without any problem with Yahoo.


Any thoughts?


Edit:

I just saw that this issue only happens with the videos taken with the camera. Some videos on Instagram stories only are pictures with animated "stickers", those videos I can see them playing, but not the rest.

Edit #2:

From time to time I can access my AOL email.

Firefox uses either Flash or HTML5 for video playback, depending on the website. In case of HTML5, the only external codecs it uses are some standard codecs from Windows. It does not use anything from K-Lite or other codec packs.

Make sure none of the standard codecs from Windows are disabled:
Codec Tweak Tool > Media Foundation
Codec Tweak Tool > MS Codec Tweaks

Since the problem is with a specific website, it is most likely caused by content blocking settings in Firefox. For example blocking trackers or third party cookies can break things on some website. If you click on the icon at the left side of the address bar in Firefox, you can adjust those settings for individual websites.
Adblocking extensions can also be the cause of course.

Thank you very much for clarifying that K-Lite has nothing to do with these problems.

I think they have been a series of circumstances that happened together by coincidence.

I can already access my AOL email, maybe it was a compatibility problem that the platform has with the browser.

And as for Instagram, as I mentioned, I already tried disabling all the add-ons. Now I see that there is a problem playing the videos on Twitter that are filmed vertically [like the stories on Instagram]. No doubt it has to do with that.

What happens on Twitter is that now those videos when I click on play, I only see everything black and there is only audio.

As far as I know there have always been problems in different browsers playing videos in vertical.

Ramon wrote:Hi

When playing Instagram stories [videos], I can only hear the audio since I updated to version 14.7.0 Mega. I can only see the frozen picture of the video with the audio.

So far this only happens with the stories on Instagaram.

Also, I update the flash using the link that you have at the home screen of the site.

I'm using Windows 7 with Firefox 65.0.2 (64-bit)

I don't know why this happens, it's the only wrong thing.

I also need to say that I try using the Firefox with all the addons and extensions disabled, and it happens the same thing.

I don't know if this is linked to the problem, but I have an AOL email account and it gets stuck on the "loading" bar and I never access to the home screen of my email on AOL, but without any problem with Yahoo.


Any thoughts?


Edit:

I just saw that this issue only happens with the videos taken with the camera. Some videos on Instagram stories only are pictures with animated "stickers", those videos I can see them playing, but not the rest.

Edit #2:

From time to time I can access my AOL email.

Hi, I have the same problem, plus Facebook Stories. It started after Firefox 63.0.3.
FF 63.0.3 doesn't have a problem with Story videos but on the newer versions of Fierfox I can't play them. (Only sound)
Chrome is working fine, but Opera has the same problem.
Have you found a solution?

Hi Emily

I've not found a solution

But there is a post on reddit about this topic. I will share the link to the comment I made on that topic:

https://www.reddit.com/r/firefox/comments/c2sc8v/twitter_gifs_never_work_all_black/ewg0j0q/

The Web Developer tools in Firefox might be helpful. For example press Ctrl+Shift+K and see if there are any errors.

Admin wrote:The Web Developer tools in Firefox might be helpful. For example press Ctrl+Shift+K and see if there are any errors.

Yes:
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).

Content Security Policy: The page’s settings blocked the loading of a resource at data:application/javascript;base64,KGZ1b… (“script-src”).

Type this in the address bar:
about:config

Set "security.csp.enable" to false.

Admin wrote:Type this in the address bar:
about:config

Set "security.csp.enable" to false.

what is that?

That option disables the feature that was causing those errors in your log. It seems it is too strict. Disabling it may solve your problem.

It didn't do anything. And after doing that now I get this error:

The connection to https://api.twitter.com/live_pipeline/events?topic=%2Ftweet_engagement%2F1172199018455130112 was interrupted while the page was loading.

And this warnings:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Source map error: TypeError: NetworkError when attempting to fetch resource.
Resource URL: https://abs.twimg.com/responsive-web/web/loader.AppModules.10466d23e1be0ced4.js
Source Map URL: https://ton.smf1.twitter.com/responsive-web-internal/sourcemaps/web/loader.AppModules.10466d23e1be0ced4.js.map

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Request to access cookie or storage on “https://www.google-analytics.com/analytics.js” was blocked because it came from a tracker and content blocking is enabled.
1172200018075426817
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.twitter.com/1.1/jot/client_event.json. (Reason: CORS request did not succeed).

Browser plugins such as NoScript can also cause things to be blocked. The blocked stuff is all third party stuff, so it shouldn't have effect on the Instagram content. You can ignore these warnings.

Admin wrote:Browser plugins such as NoScript can also cause things to be blocked. The blocked stuff is all third party stuff, so it shouldn't have effect on the Instagram content. You can ignore these warnings.

I've tried firefox on "safe mode" without any complements, but nothing

Which graphics card do you have? Updating the driver might help.

Admin wrote:Which graphics card do you have? Updating the driver might help.

Some weeks ago I update the driver of my graphics card. I have an Nvidia and I use the GeForce Experience v3.19.0.107 to update.