We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

FreeVerse Movie site on Amazon won't play.

  • 7 antwurd
  • 0 hawwe dit probleem
  • 27 werjeftes
  • Lêste antwurd fan zeroknight

more options

When I play Freeverse on Amazon to see a movie with ads, it stops at the ads and says PLAYER UNAVAILABLE. Happened on latest release 115.0.2 (64 bit).

When I play Freeverse on Amazon to see a movie with ads, it stops at the ads and says PLAYER UNAVAILABLE. Happened on latest release 115.0.2 (64 bit).

Alle antwurden (7)

more options

Sounds like the site player is incompatible with something in the Browser itself. Link helps others see what is going on here.

more options

Does it still happen in Troubleshoot Mode?

more options

Tried Troubleshoot mode and no soap. Just happened with this recent update. I turned off enhancements and that didn't solve it either. Only on FreeVerse so far. Works fine for other streaming.

more options

It is Prime on Amazon which has FreeVerse hooked it. Prime itself is posing no problem and everything worked until this last update. That is all I can tell you. I'm using Chrome now anyway and it doesn't seem to have a problem with it. I tried Edge too and no problem.

more options

Does it still happen in a new profile? An easy way to get a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.

more options

Nope, didn't work. I'm using Chrome for Freeverse. I appreciate all the help, but I want to watch them and to keep replaying the same movie may draw unwanted attention. As I see it FireFox changed something and I can't unchange it.

more options

You can test older versions with mozregression to find exactly when the problem started.