3/15/2024 0 Comments Google drive downSince then I've helped him work on his server periodically. He told me the scanner would periodically stop scanning around the same time, and when he contacted support for the VPS they told him it was the Google API limitation maxing out. When he first started out with his Plex server he had a ton of stuff to scan in for metadata, and access to the media files that were linked through Rclone kept going down. I'm actually trying to help a friend move his Plex server off of a VPS service to his own private machine. For now, we have to resort to the unpleasant workaround described above to let people enjoy these videos.I think I may have solved my own problem without realizing it, but I'll try to give more context. This has been reported by multiple people on StackOverflow, Apple User Community, and Github, with no known fix. They would probably encourage us to use YouTube instead, which is not an option for most of our videos. Unfortunately, this use case isn't a typical one for Google Drive and hence, this is probably super low on the Drive team's priority list and unlikely to ever get fixed. If Google Drive were to support this -like YouTube or Facebook do- ITP would not block cookie access, and the videos would play just fine. It involves using a a dedicated Storage Access API, which specifically supports third-party embeds which are invoked by a user action (in our case, clicking the Play button on the video). ITP has a way to prevent this from happening for legitimate use cases like this one. This is blocked by Safari ITP, resulting in the error in video playback that your experienced. Because this website is not hosted on, Google's cookies are considered "third-party cookies" and reading them on this website is considered "cross-site tracking" by Safari. To achieve this, Drive will try and read your Google cookies to find what your Google User ID is. But no matter, Drive will try and check this all the time anyway. In this website's case, this check is useless as all videos are public and hence, don't need to know who you are to be played. This is because Drive is not usually used to share things publicly. Indeed, Google Drive needs to know what your Google account is to check if you have permission to watch shared videos. In short, because of a bad handling of Safari's Intelligent Tracking Prevention (ITP) by Google Drive. Scroll down to the "Privacy & Security" section and un-toggle "Prevent Cross-Site Tracking".Your only option on iOS/iPad OS is to turn off Cross-site tracking prevention on Safari to watch the video - you can safely turn it back on after watching. Reload the page and the video should now play fine. Go to Safari Preferences > Privacy and uncheck "Prevent cross-site tracking". Option 2: Turn off "Prevent cross-site tracking" on SafariĪnother workaround is to (temporarily) turn off the Safari feature that is causing the problem. If you can switch to a different browser, such as Chrome or Firefox, you should be able to play the video without hiccups. The issue is due to a poor support of one of Safari's privacy features (see below for details). How to fix On Mac/PC Option 1: Use Chrome or Firefox
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |