I have developed a service that operates multiple rclone config files. Upon receiving a request, rclone runs check command with box remote. It works fine for one hour, but then access token expires and refresh token does not refresh access token.
I thought running any Rclone command will refresh a token in the given config file.
Is this expected behaviour?
What is your rclone version (output from rclone version)
rclone v1.52.2
os/arch: linux/amd64
go version: go1.14.4
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Alpine linux latest
Which cloud storage system are you using? (eg Google Drive)
Box
The command you were trying to run (eg rclone copy /tmp remote:tmp)
Rclone check
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
2020/07/20 10:01:12 DEBUG : rclone: Version "v1.52.2" starting with parameters ["rclone" "ls" "box:SyncTest" "-vv" "--config=/configs/domesticus.conf"]
2020/07/20 10:01:12 DEBUG : Using config file from "/configs/domesticus.conf"
24363 unnamed.png
│
2020/07/20 10:01:13 DEBUG : 5 go routines active
I am using separate configs, but from time to time rclone fails to update token in a config. I did not receive any error messages or whatsoever. I randomly get invalid refresh token.
It's hard to capture this issue, because it randomly occurs.
I have found a workaround btw. For the same box app I have created a JWT token. Using --box-box-config-file flag I provide this json file and tokens seem to update correctly