Together with -tpslimit flag, this results in so much reduction of total 403 and 5xx error. I wish this is turned On by default setting. Welcome to Android Central First, go to Settings>Accounts-Google>your Google account, and uncheck. This result in much cleaner DRIVE API dashboard. How do you stop Google Drive from uploading files. So this minimizes the number of 403 error rate I have been receiving. To restrict the user from downloading and uploading documents in Google Drive, you can create a category and add it to a policy in the Smoothwall Filter and. The pattern of the 403 error is also the same, 20% error rate for almost all day long, spiked into 100% error before being reset.īy using this flag, it looks like that once it reaches 750gb and receive error, it becomes fatal error and kill the process. Run the Google Drive app on your Android mobile and tap on the menu button (it’s the three-bar icon) at the top-left of the screen. So, when it comes to fixing Google Drive’s performance, you have to clear both caches. To stop the file from uploading at all, tap the X at the bottom-right. To unpause/restart the upload, tap Upload paused at the bottom of each file. It’s the two vertical lines at the bottom-right corner of each file. So in the dashboard for each of Google account, the graph is always full of 403 error because I use up 750gb limit just within few hours every day. Google Drive comes with a built-in cache manager that is separate from Android’s cache. Tap the pause icon on any file you want to pause. Then around uploading 740GB the 403 userratelimit exceeded error rate jumps to 100% before the process is killed or stayed like that until 750GB limit is reset. Uploading speed is throttled at this time (by Google?). So for example near uploading 700GB, I always have constant error 403 userratelimit exceeded for almost all day for constant 20% of total all requests. In my case, before I use this flag whenever I uploaded more than 750GB limit of either server-side or non-server-side, I always get 403 errors due to each Google account is heavily being used. But after few hours it starts normally by itself. There are times when using this flag caused rclone to do nothing for few hours at the start time, no logs at all even with using -vv flag. The error you have above is a normal slow down messageĮspecially if you want to reduce error rate per hour.
0 Comments
Leave a Reply. |