Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

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
  • 235 views
  • Last reply by Amelia

bach9112
bach9112

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)

Amelia
Amelia

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