Currently, the google drive access tokens are revoked very quickly, sometimes even within one day. Is there a way to extend them?
There's no reason to as you'll get a new token with a refresh token.
felix@gemini:/opt/rclone$ rclone about GD: -vv 2023/02/16 20:45:56 DEBUG : Setting --config "/opt/rclone/rclone.conf" from environment variable RCLONE_CONFIG="/opt/rclone/rclone.conf" 2023/02/16 20:45:56 DEBUG : rclone: Version "v1.61.1" starting with parameters ["rclone" "about" "GD:" "-vv"] 2023/02/16 20:45:56 DEBUG : Creating backend with remote "GD:" 2023/02/16 20:45:56 DEBUG : Using config file from "/opt/rclone/rclone.conf" 2023/02/16 20:45:56 DEBUG : GD: Loaded invalid token from config file - ignoring 2023/02/16 20:45:56 DEBUG : Saving config "token" in section "GD" of the config file 2023/02/16 20:45:56 DEBUG : Keeping previous permissions for config file: -rwxrwxr-x 2023/02/16 20:45:56 DEBUG : GD: Saved new token in config file Total: 16 GiB Used: 1.863 GiB Free: 10.685 GiB Trashed: 2.587 KiB Other: 3.452 GiB 2023/02/16 20:45:56 DEBUG : 6 go routines active
I see, could there be any possibility for the refresh token to fail at refreshing?
"any" - yes, network errors, client ID revoked, DNS issues, not using it for a long period of time (not sure the exact number as I've not used my Google Drive for over 30 days and had no issues).
Generally though, the refresh tokens work as expected and they are all done per Google's requirements in this case so you can't really do much to change it.
If it was something non expiring ever, a service account is the way to go.
It could be the app type that blocks the refresh status, I have adjusted my project to published to see if it will work. Thank you!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.