Cannot get authorization to the Google OAuth consent screen, 400 error.

[5536086]

Cannot get authorization to the Google OAuth consent screen, 400 error.

The content in this section has been provided by the app developer. This content has not been reviewed or verified by Google.

[MTrab]

+1

[russellwilson01]

rclone implemented fixes for this, looks like google deprecated the oob workflows;

https://forum.rclone.org/t/google-drive-oauth-with-non-interactive-no-longer-works/29626

[5536086]

设置应用为测试版，将自己谷歌账号添加到应用中即可

测试版应用token有效期只有7天，七天后过期失效

[Overbull]

+1

[Eleatmelon]

I have the same problem and the project does need a fix.

[5536086]

I have the same problem and the project does need a fix.

Use the latest version of rclone, license it locally, and copy the relevant information to the configuration folder of plexdrive, which is the solution available now

[nephariouz]

Use the latest version of rclone, license it locally, and copy the relevant information to the configuration folder of plexdrive, which is the solution available now

Can you elaborate on this solution?
What's the relevant info? What file does it go in and what's the format?
I have a working rclone.conf file from a previous install but I'm not sure what plexdrive needs from it or where to put it.
I've never used plexdrive before so I'm not sure what a complete config.json file looks like (assuming that's even where it goes)

[OzanMakinaci]

Here's what I think he means (this worked for me). When you install plexdrive it will create a directory with its configuration files (by default ~/.plexdrive). In there you will see two files of note:

• config.json --> contains the client ID and client secret of the Google Cloud credentials to use
• token.json --> contains the access_token details (provided by Google Cloud when to authenticate using the Client ID and Client Secret)

Essentially, the method of authenticating (to obtain the token) that Plexdrive can do is no longer allowed by Google Cloud. However, RClone has built a new method of authentication and when you use that it creates the config.json and token.json files that you can transfer over to the plexdrive config directory.

So you need to install and configure rclone anywhere else as per their instructions and then grab the config.json and token.json and copy them to replace the plexdrive ones.

This would allow plexdrive to keep working without disrupting things.

I am skipping over the whole "how to install and configure rclone" because they have plenty of instructions on that already. Specifically these pages:

• Install -> https://rclone.org/install/
• Configure Google Drive -> https://rclone.org/drive/

Hope that helps!

[mrjustintime]

Using the workaround above from @OzanMakinaci did work for me, but with an annoying problem. Refreshing the token is not automated in this case, so I had to deal with very low token lifespan (something near 30 minutes I think). After that the access is being denied, which can't really be visualized by Plex (it's far too low level · like filesystem level).

Today I checked the same setup using the release version 5.2.1 and it seems to be no problem anymore. So I think, there are two possible reasons:

1. The project used today may be different to the project used a few days ago, therefore Google could be allowing this authorization method for already existing accounts within a grace time, or
2. Google did roll back this change after some angry feedback.

Anyone having the same experience or more information?

EDIT

Additionally removing config.json from ~/.plexdrive seems to start a different setup process than just deleting token.json. Deleting just the token configuration does indeed trigger the problematic process, but when all config is removed, the "setup wizard" seems to choose a different, working approach.

[saitoh183]

So, i got the email about the Auth change and i sent in for the time extension. I wanted to know does this only affect people wanting to create a new connection with plexdrive or if affect connections already establish? Do i have to re-auth my plexdrive (still using 4.0 and 5.0...no reason to change since it works) using @OzanMakinaci method?

[OzanMakinaci]

Hmmm... I'm not sure if this change will invalidate the existing solutions that use the refresh token to obtain continued access. You could be right in that this only impacts people going through the initial credential setup. I suppose by now you should now since Oct 3, 2022 was the final action date from Google.

Does your plexdrive continue to work @saitoh183?

[saitoh183]

Hmmm... I'm not sure if this change will invalidate the existing solutions that use the refresh token to obtain continued access. You could be right in that this only impacts people going through the initial credential setup. I suppose by now you should now since Oct 3, 2022 was the final action date from Google.

Does your plexdrive continue to work @saitoh183?

So I got confirmation that you would need to redo your auth on existing connections. I did the auth method and it did work.( plexdrive 4 and 5) I also had asked google for the extension till january in case it didnt work so i would have time to figure something out. But i decided to move to rclone VFS with rclone union and moved all my data to shared drives (Team drives) so i can utilise autoscan since plex_autoscan is going to be dead in the water (plex deprecating scan & refresh CLI) and is not supported anymore.

[hbbernardo]

How can I grab the config,json and token,json from another rclone installation?

[mrjustintime]

How can I grab the config,json and token,json from another rclone installation?

@hbbernardo It can be found in your rclone config file (e.g. under ~/.config/rclone/rclone.conf). Your drive configuration has to have a field named 'token', containing the full json you can use in plexdrive. Please note, this is only the content of the token.json file.

[alneven]

I'm in the process to install my PMS setup with plexdrive, rclone and everything to a new machine.
And came here to check the development of plexdrive.
As I'm a very pleased customer :)

And want to move plexdrive also to my new setup. As it was easy to configure and to operate this solution.

I was wondering what you have here as a problem. As my config and token json are 6 years old, and my plexdrive setup is still up and running and working.
Strange. But I hope I can move those files with all the settings to the new machine, and don't have to look for a new solution, nor a workaround.