New installation of 1.56.2 failing with invalid_client on macOS

What is the problem you are having with rclone?

Trying for the first time and followed the rclone config wizard:

  1. Created new client id and secret on Google.
  2. Enabled the app.
  3. Selected Google Drive. Scope 1. Blank root folder. Service Account Credentials JSON file path is blank.
  4. No advanced config. Used auto config.
  5. Provided client id and secret to the wizard.
  6. Browser opened automatically and I received:
    Authorization Error
    Error 401: invalid_client
    The OAuth client was not found.

The terminal is waiting with:

2021/10/08 18:31:26 NOTICE: Make sure your Redirect URL is set to "urn:ietf:wg:oauth:2.0:oob" in your custom config.
2021/10/08 18:31:26 NOTICE: If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth?state=udDT9OqOBut6C0upBq-yMg
2021/10/08 18:31:26 NOTICE: Log in and authorize rclone for access
2021/10/08 18:31:26 NOTICE: Waiting for code...

Examined other threads here and the release notes for 1.56.2 and they don't seem relevant to this issue.

Any ideas on what's not right?

What is your rclone version (output from rclone version)

% rclone version

rclone v1.56.2

  • os/version: darwin 11.5.2 (64 bit)
  • os/kernel: 20.6.0 (x86_64)
  • os/type: darwin
  • os/arch: amd64
  • go/version: go1.16.8
  • go/linking: dynamic
  • go/tags: cmount

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

Google Drive

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

rclone config

The rclone config contents with secrets removed.

Was not able to get through the config process.

A log from the command with the -vv flag

Was not able to get through the config process.

hello and welcome to the forum,

looks like there is any issue with the client id, perhaps copy/paste issue?

please post the entire rclone config text, redact id/secret/password/token

here is what it a good config file would look like

[gdrive]
type = drive
client_id = 113350617813-8v2pb7jfp4568r5hh6hbbd8m9bje09lo.apps.googleusercontent.com
client_secret = jaSuAdfEROhnffQM6TvO1o60
scope = drive
token = {"access_token":"ya29.222rdaM81JMY07dXYobd0BXoamkab1to831jiKGOiQj6KLB1oBmzhgV1ouXW3CKIE_O4Rt4R9JDKSsZJu9u6It2ddd0ETWhvc7fdlSY5nvMQCXqLA1nijy-RmGRZ_XmZ0w_YHOpfoF6wfffNIVZ8VSmYhNdVmpg","token_type":"Bearer","refresh_token":"1//0h9C5MPJwUJo4CgYI112ZAGBE1wwedF-L9Ir4NoazoXYt811wEHhAegRcmjISmndFatlUt_SYstasLG_zDjILrRxoeql4UKhWSsaR02k","expiry":"2021-10-04T15:04:51.7458998-04:00"}

Hi, and thank you for the welcome and the help.

There is no config file yet:
cat Users/andreangelantoni/.config/rclone/rclone.conf
cat: Users/andreangelantoni/.config/rclone/rclone.conf: No such file or directory

I've done this twice and I'm sure there is no copy paste error. I don't get through the configuration.

i understand there is no config file yet, as you cannot create it

post the text for the rclone config command.

also, as a test, create a gdrive remote without a client id/secret.

rclone config

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q> n
name> gdrivetest
Type of storage to configure.
Storage> drive
Google Application Client Id
client_id> 113350617813-8v2pb7jfp4568r5hh6hbbd8m9bje09lo.apps.googleusercontent.com
client_secret> jaSuAdfEROhnffQM6TvO1o60
Scope that rclone should use when requesting access from drive.
scope> 1
root_folder_id>
service_account_file>
Edit advanced config?
y) Yes
n) No (default)
y/n>
Use auto config?
 * Say Y if not sure
 * Say N if you are working on a remote or headless machine

y) Yes (default)
n) No
y/n> y
2021/10/09 11:47:11 NOTICE: Make sure your Redirect URL is set to "urn:ietf:wg:oauth:2.0:oob" in your custom config.
2021/10/09 11:47:11 NOTICE: If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth?state=DUDF-qdMZrKaGuyHst938A
2021/10/09 11:47:11 NOTICE: Log in and authorize rclone for access
2021/10/09 11:47:11 NOTICE: Waiting for code...

Well, there you go: this morning running through it again it's now working for me.

Thank you for the help. It appears to be something was up with Google.

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