Avatar for Username

Search Support

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.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

"Video cannot be played on your device as it does not meet content protection stamdards"

  • 1 eyano
  • 0 eza na bankokoso oyo
  • 6 views
  • Eyano yasuka ya jonzn4SUSE

pete-sage
pete-sage
more options

Problem: "Video cannot be played on your device as it does not meet content protection standards" Message when trying to stream videos but only on Amazon Prime.

I have searched the internet for an answer only to be told the problem lies in the browser. I find this confusing because a few months ago I was always watching Amazon Prime videos on Firefox browser. What has changed? How can I correct it? I have the latest Firefox update (108.0.1 64 bit) on my mac Book Pro, MacOS Ventura 13.1.

Thanks for any help you may be able to offer,

Happy Christmas,

Pete



/edit: move thread from Firefox for iOS (iPhone/iPad) to (desktop) Firefox section as you have macOS

Problem: "Video cannot be played on your device as it does not meet content protection standards" Message when trying to stream videos but only on Amazon Prime. I have searched the internet for an answer only to be told the problem lies in the browser. I find this confusing because a few months ago I was always watching Amazon Prime videos on Firefox browser. What has changed? How can I correct it? I have the latest Firefox update (108.0.1 64 bit) on my mac Book Pro, MacOS Ventura 13.1. Thanks for any help you may be able to offer, Happy Christmas, Pete /edit: move thread from Firefox for iOS (iPhone/iPad) to (desktop) Firefox section as you have <b>macOS</b>

Ezalaki modifié na James

All Replies (1)

jonzn4SUSE
jonzn4SUSE
  • Top 10 Contributor
more options

Did you try with Firefox in Safe Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode

I'm on a mac running 10.13.6 and it works for me. see screenshot