Brief: Firefox now enables you to play DRM content. This means you can watch Netflix on Firefox in Linux without painful workarounds.
Perhaps the easiest way to watch Netflix on Linux is to install Google Chrome. For a long time, only Google Chrome was able to play Netflix videos on Linux. The main reason behind other prominent browsers such as Chromium and Firefox not playing Netflix videos relates to DRM.
DRM (Digital Rights Management) is the generic term used for technologies that control how users can use a digital media. The main aim is to protect the digital product from being copied, shared and pirated. It also enables the provider to restrict the content on their specific device.
For example, if you own a Kindle and ‘buy’ books from Amazon, you cannot read the eBook you bought on Amazon on a non-Amazon device such as Kobo. It’s as if you don’t even own the book you actually purchased. Issues like this are reasons why DRM has been constantly criticized by open source advocates.
In March 2017, Netflix announced the news that Netflix can be played on Firefox in Linux, without any gimmickry. All you have to do is to enable DRM.
How to play Netflix using Firefox on Linux
Today, if you try to play Netflix, you may see an error like this:
The error reads:
Whoops, something went wrong... Playback Error There appears to be a problem with Firefox that is preventing Netflix from starting playback. Please ensure that you are on the latest version of Firefox. Error Code: F7702-1003
The reason behind this error is that you don’t have DRM enabled and thus you are missing Widevine plugin to decode the DRM protected Netflix content. It is the same if you try playing Spotify web player.
Let me show you how to enable DRM content playback on Firefox to watch Netflix or Spotify.
Step 1: Enable DRM
Open Firefox and type about:preferences#content in the address bar. Look for Digital Rights Management (DRM) Content field and check the box in front of Play DRM-controlled content.
This will start to install the Widevine plugin from Google. Depending on your network speed it will take a few minutes to install this add-on.
Step 2: Make sure that you have the required add-ons
It is always better to ensure that you have the right tools. Open a new tab in Firefox and type about:addons in the address bar. Make sure that you have Widevine and OpenH264 add-ons installed with ‘Always Active’ mode.
Restart Firefox if required. You should now be able to play Netflix or Spotify or other websites using DRM protected content.
Possible troubleshoot
As an It’s FOSS reader noted, you may need the right codecs. You can install this in Ubuntu-based distributions using this command and then repeat the above mentioned procedure:
sudo apt install libavcodec-extra
What’s your say?
I know that DRM is a touchy issue and not everyone will be happy about Mozilla compromising on its earlier stand on DRM. But considering that EME is an HTML5 standard now, I think it was inevitable. At least, end users can play Netflix and Amazon Videos with Firefox now.
How about you? Did you manage to play Netflix on Firefox? Do share your experience.
It doesn’t work FF69, ubuntu 19.10
Some suggestions for improving the post:
The codecs needed for fedora is ffmpeg (dnf install ffmpeg)
If someone still has trouble, the solution can be:
Temporarly disable selinux (sudo setenforce 0), this affect some fedora 30 users and maybe others. It is documented here: https://bugzilla.redhat.com/show_bug.cgi?id=1731371
Also, to check if the firefox profile is a problem: firefox -P -new-instance. This needs reenabling of the DRM setting
“Digital Rights Management (DRM) Content” options doesn’t appear in my version of Firefox on Ubuntu 18-04. How do I get a version of Firefox that has it?
What version of Firefox are you using?
Having same issue ( no DRM check box ) on Raspbian. Version is Firefox-ESR 60.9
I can confirm that on a fresh install of Pop_OS! (Ubuntu 19.04) it is needed to install libavcodec-extra -package to get Netflix up and running. Firefox prompts for DRM so it’s installation can be handled from the browser itself.
Thanks for confirming that, Peetu.