55

Jai-jdk
Those gave the same error messages, so it might be something that needs chrome settings to be accessible, so that Netflix can understand that playing protected content has been enabled in this browser

    Tried a couple others made for Netflix, and they didn't work

      7 days later

      Bump - also having this issue. I've tried changing the user agent to many different browsers, including my local safari's user agent.

        Ok update, Disney+ is also giving an error. Hulu plays everything but refuses to stream at HD level quality, which leads me to believe this might be a FairPlay/Widevine or other DRM related issue.

        Edit: YouTube works fine at all quality levels up to 4k.

          Also have that issue and it is annoying. I tried switching the UA but that is not working for me. I activated compability Mode and this was also not fixing the Issue

            HBO Max also does not seem to work with some videos. It will open, but display a black loading screen. Interestingly, I can see the subtitles... Works great on brave but does not seem to work on Orion. I have tried changing the UA but no luck 🙁

              Hi I get the same error on Netflix tried with compatible mode, but then I no longer get error code. But I only get a black screen and only audio works. I just want to reply on this so you guys are notified. I do have one more issue when I watch Youtube in full screen mode the screen flickers every couple of seconds. It started after I updated to macOS ventura. I do not know how to show it or add technical info but I also tried in compatible mode and different user agents. But I got the same results .

                Should be fixed in the next release (updated WebKit)

                  5 days later
                  6 days later

                  Does that mean that an update is available yet?

                    Just downloaded the latest version and issue still occurs..

                      My bad, this is fixed in the upcoming release.

                      Hi @Vlad I'm happy to see this issue was solved in the release notes. When will we get the update?