Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Prime Video not loading video pages: "That shouldn't have happened" error

  • 1 risposta
  • 0 hanno questo problema
  • 8 visualizzazioni
  • Ultima risposta di gwendrenee

more options

I am unable to load the video pages on prime video in firefox. Instead of loading the video's page, it gives me a black screen and says "That shouldnt' have happened. It looks like something went wrong on our side. Let's find you a great video to watch instead." It works fine in Chrome, and other streaming sites like Netflix also work. I tried upgrading firefox, and upgraded to 129.0 (64 bit), but the same error is still happening. I contacted Amazon support, they couldn't figure it out, and told me to talk to Firefox support.

I disabled ublock origin, and disabled trackign protection, and error still occurs.

I am unable to load the video pages on prime video in firefox. Instead of loading the video's page, it gives me a black screen and says "That shouldnt' have happened. It looks like something went wrong on our side. Let's find you a great video to watch instead." It works fine in Chrome, and other streaming sites like Netflix also work. I tried upgrading firefox, and upgraded to 129.0 (64 bit), but the same error is still happening. I contacted Amazon support, they couldn't figure it out, and told me to talk to Firefox support. I disabled ublock origin, and disabled trackign protection, and error still occurs.
Immagini allegate

Tutte le risposte (1)

more options

Update: I was able to trace the problem to the extension "ClearURLs", disabling it fixes the problem. I submitted an error report for the addon.

Modificato da gwendrenee il