What is the problem you are having with rclone?
No real "problem", just trying to debug why Google Drive API console shows that rclone is getting 302 response codes in about the same amounts as the 200s.
--log-level DEBUG doesn't give anything relevant, eg it doesn't show any actual requests to Drive API nor response codes. (Is there any simple way to get this information other than wiresharing the packets?)
Is the 302 a problem? Maybe not, it just seems weird that basically all requests are getting a 302 Found
... or is that expected behavior from Drive API? I don't think the rest of the template is so useful, but I filled it in anyways. Thanks for any insight!
Run the command 'rclone version' and share the full output of the command.
rclone v1.67.0
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.15.0-113-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.22.4
- go/linking: static
- go/tags: none
Which cloud storage system are you using? (eg Google Drive)
Google Drive with my own API key.
The command you were trying to run (eg rclone copy /tmp remote:tmp
)
rclone mount drivemount: /media/Drive/ --allow-other --dir-cache-time 300m -P --umask 002 --log-level INFO --stats 30s --vfs-read-chunk-size 1M --stats-file-name-length 0
Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
[drivemount]
type = drive
scope = drive
token = XXX
chunk_size = 32M
root_folder_id = XXX
client_id = XXX
client_secret = XXX
team_drive =