On Monday September 25th from 10PM EDT - 12AM EDT (2AM UTC - 4AM UTC on September 26th), we will be performing system maintenance on the Firefox Accounts databases for two hours. During the maintenance window, there will be brief periods of a few minutes where users will not be able to login to their accounts. Please try again at a later time.

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

Firefox will not play Netflix, Hulu or Disney. Edge does. You recently updated my Firefox to 96.0 64 bit

  • 1 reply
  • 1 has this problem
  • 1199 views
  • Last reply by Amelia

more options

Firefox will not play Netflix, Hulu or Disney. Edge does. You recently updated my Firefox to 96.0 64 bit. Netflix gives this error

Secure Connection Failed

An error occurred during a connection to www.netflix.com. PR_END_OF_FILE_ERROR

   The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
   Please contact the website owners to inform them of this problem.

Learn more…

Firefox will not play Netflix, Hulu or Disney. Edge does. You recently updated my Firefox to 96.0 64 bit. Netflix gives this error Secure Connection Failed An error occurred during a connection to www.netflix.com. PR_END_OF_FILE_ERROR The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Learn more…

Chosen solution

Hello,

This is not fault of the new update. This error can be caused by many things, but I think that the easiest one to start with is disabling DoH. It is a measure that although secures your dns queries, may not be the best for errors like this. To do this, go to about:preferences#general and find the network settings. Click on change settings and turn off DNS over HTTPS.

More information about DNS over HTTPS can be found at DNS-over-HTTPS (DoH) FAQs

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

Hello,

This is not fault of the new update. This error can be caused by many things, but I think that the easiest one to start with is disabling DoH. It is a measure that although secures your dns queries, may not be the best for errors like this. To do this, go to about:preferences#general and find the network settings. Click on change settings and turn off DNS over HTTPS.

More information about DNS over HTTPS can be found at DNS-over-HTTPS (DoH) FAQs