Because there is a well known issue with some mediaplayers on at least some formats that struggle to stream from a Gdrive because they use a read-method that opens the file - reads only a little bit - then closes it, and then reopens it again ect. This not only leads to horribly stuttery playback but also massive amounts of requests for the same file.
Even if only tiny sections are read each time it may easily register as a mass-leech if the Google servers see thousands of accesses to the same file in a short period. Generally Plex should be capable of streaming it fine, but if this was a user outside your control that might have loaded the stream in some other mediaplayer or something is that possible Animosity? I doubt this is the problem. I don't think GDS syncs anything, at least by default.
What it does is basically indexing and listing any changes. This is a trivial data-size, and besides listing data would not count against your quota - just require some API calls.
I am of course making some assumptions here on how GDS works because I obviously don't know the internal logic, but I think the assumptions are fairly safe to make. That should make it a lot more managable to share. I just woke up and started seeing downloadQuotaExceeded errors and also saw some User Rate Limit Exceeded errors as well.
It appears it's not a full 24hr lockout this time, I'm currently able to play a file for the past minutes or so, and when this happened last time I was unable to get anything started hours after I got the errors. I just have no idea why this is happening, and if there's anything I could do to stop it from happening.
Any help trying to diagnose this would be greatly appreciated. After looking around it seems there were issues with some Google services this morning around am CST, probably as a result of more people working and having schools switch to online. This spesific error is from the API if it is getting too many requests too fast - but it definitely not critical.
Rclone just uses these as "hey, slow down a bit" indicators and will adjust it's rate of requests automatically in most remotes. If you see way more retries than that then something is hammering the API bad and something may be wrong. You get requests pr seconds, so this error will not persist very long at all - not unless something is going haywire in application software using rclone.
This is the same issue as before almost certainly or otherwise it would have to be the general 10TB download quota, which seems very unlikely in your case. Can you identify from the Plex, rclone and Google Gdrive metrics a spesific client that is causing the issue? Thank you! Start a conversation. Copy link. Software deals Friday round-up.
I agree with the Privacy Policy regarding my personal data. More on this Topic December 9, This message can prevent you from accessing your files. Read More. November 16, Fix it right away with one of our detailed solutions. This mode is the best way to avoid all the concerns related to browsers. In Google Chrome, you can click the 3-dot menu and choose New incognito window. Next, sign in and try downloading files from Google Drive.
Noosrep Noosrep 1, 5 5 gold badges 20 20 silver badges 38 38 bronze badges. Add a comment. Active Oldest Votes. To get that, Open the URL in either of the browser. Go to Network tab. Now click on download. Saving file isn't required. We only need the network activity while browser requests the file from the server. A new entry will appear which would look like " download. Paste the copied content directly in the terminal and append --output file.
Improve this answer. The possible reasons for Google Drive error are the problem with your browser caching, multiple Google accounts signing in, etc. If you often use Google Drive, your browser is likely to have cookies or cache bug that experiences the error. Thus, you can clear the cache to get rid of Google Drive error Here, take Google Chrome as an example.
Step 2: Select All time as the time range, focus on Cookies and other site data and Cached images and files , then click Clear data. Step 3: Re-launch the browser and sign in your Google Account.
0コメント