Couldn't decode response - try again (make sure you are using a matching version of rclone on both sides: invalid character 'e' looking for beginning of value

Help and Support
1

What is the problem you are having with rclone?

Couldn't decode response - try again (make sure you are using a matching version of rclone on both sides: invalid character 'e' looking for beginning of value

Run the command 'rclone version' and share the full output of the command.

Which cloud storage system are you using? (eg Google Drive)

onedrive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

Paste command here

The rclone config contents with secrets removed.

Paste config here

A log from the command with the -vv flag

Paste  log here

=================================
When I use onedrive private api，it said Couldn't decode response - try again (make sure you are using a matching version of rclone on both sides: invalid character 'e' looking for beginning of value

I have creat client and key.

021322290570_01
021322290570_011595×2718 436 KB

2

I can't begin to read any of those screenshots so without being to know the information in the post, I can't help.

3

hello and welcome to the forum,
--- is there a specific reason to use a beta version of rclone,
best to use latest stable, v1.57.0 on both machines.
--- the error could be a simple copy/paste error.
--- are both machines running the same operating system?

might be easier to
--- run rclone config on the machine with the web browser and choose auto config.
--- copy the rclone.conf from that machine to the headless machine.

and if that does not solve the issue, then need to post
--- output of rclone version on both machines
--- a full debug log , add -vv to the command.

please do not use hard to read screenshots, just copy and paste the text.
enclose the text with three backticks so the output is formatted like this.

rclone v1.57.0
- os/version: ubuntu 20.04 (64 bit)
- os/kernel: 5.10.60.1-microsoft-standard-WSL2 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.17.2
- go/linking: static
- go/tags: none
4

I think this is the token size bigger than the input buffer problem. There is an issue about this here

To work around, configure the remote by making the config file locally then copying it to the remote end.

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.