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.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Ova tema je arhivirana. Pitajte drugo pitanje ako vam je potrebna pomoć.

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

  • 1 odgovor
  • 0 ima ovaj problem
  • 8 views
  • Posljednji odgovor poslao gwendrenee

gwendrenee
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.
Priloženi snimci ekrana

All Replies (1)

gwendrenee
gwendrenee Vlasnik pitanja
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.

Izmjenjeno od strane gwendrenee