accès denied

[lexo13]

grive version 0.5.2-dev Nov 13 2019 10:41:39
current time: 2019-11-13T15:22:41.889Z
config file name "./.grive"
logging HTTP response: http2019-11-13.152241.txt
HTTP POST "https://accounts.google.com/o/oauth2/token"
HTTP response 401
Failed to refresh auth token: HTTP 401, body: {
  "error": "unauthorized_client",
  "error_description": "Unauthorized"
}
exception: /build/grive2-8oi0wE/grive2-0.5.2/libgrive/src/protocol/OAuth2.cc(111): Throw in function void gr::OAuth2::Refresh()
Dynamic exception type: boost::exception_detail::clone_impl<gr::OAuth2::AuthFailed>
[gr::expt::BacktraceTag*] = #0 0x58f113 grive gr::Exception::Exception()
#1 0x56c0a5 grive gr::OAuth2::AuthFailed::AuthFailed()
#2 0x56bd76 grive gr::OAuth2::Refresh()
#3 0x56b116 grive gr::OAuth2::OAuth2(gr::http::Agent*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
#4 0x51264e grive Main(int, char**)
#5 0x5131d4 grive main
#6 0x7f10e1c4d830 /lib/x86_64-linux-gnu/libc.so.6 __libc_start_main
#7 0x511159 grive _start

[Boseka]

i'm getting the same issue !!

tried to reauthenticate, to reinstall ... the same shit

[jfernandoghe]

Same issue, tried to Re-Auth and Re-Ins.... but it's still not working... any solution?

[wdysun]

same issue here

I also re-did the authorization thing, going in google panel says "grive2 connected to your account". I did a system update this morning and therefore i am running

"grive version 0.5.2-dev Nov 13 2019 10:41:39"

[saidone75]

"grive version 0.5.2-dev Nov 13 2019 10:41:39"

Same version, same issue.

[hubyhuby]

Similar issue here with update today 0.5.2 on Ubuntu 18.04 (was working previousely for 1 year)

/grive$ grive
Failed to refresh auth token: HTTP 401, body: {
"error": "unauthorized_client",
"error_description": "Unauthorized"
}
exception: /build/grive2-RRCxdx/grive2-0.5.2/libgrive/src/protocol/OAuth2.cc(111): Throw in function void gr::OAuth2::Refresh()
Dynamic exception type: boost::exception_detail::clone_implgr::OAuth2::AuthFailed
[gr::expt::BacktraceTag*] = #0 0x563df783195d grive gr::Exception::Exception()
#1 0x563df781499d grive gr::OAuth2::AuthFailed::AuthFailed()
#2 0x563df781461a grive gr::OAuth2::Refresh()
#3 0x563df781396c grive gr::OAuth2::OAuth2(gr::http::Agent*, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)
#4 0x563df77cef31 grive Main(int, char**)
#5 0x563df77cfab2 grive main
#6 0x7f3c44275b97 /lib/x86_64-linux-gnu/libc.so.6 __libc_start_main
#7 0x563df77cd97a grive _start

[vitalif]

See #287.

[Organic-Marble]

same on 11/15

[davama]

No change with latest master branch 👎

grive -v
grive version 0.5.2-dev Nov 15 2019 15:25:07

[vitalif]

Does that mean you still see the "login temporary disabled" screen?

[Boseka]

It works again for meeeee !!!
Thanks to whoever fixed it !!

[davama]

That’s interesting. The last commit was 4 days ago...and it was a version change.

I had tried the current master branch too and still no good. :(

[Boseka]

That’s interesting. The last commit was 4 days ago...and it was a version change.

I had tried the current master branch too and still no good. :(

I removed it yesterday and started looking for alternatives, i tried rclone and that went wrong AF, i almost lost all my locally stored files ....
Tried VGrive and ODrive but maaan they are horribly slow ....

Today desperately reinstated it from https://launchpad.net/~nilarimogard/+archive/ubuntu/webupd8/+index?batch=75&memo=75&start=75

Configured it
And it just worked

[vitalif]

1. go and blame google. I'm not responsible for the fact that they disable drive APIs for people

2. as a temporary workaround you can register your own client_id + client_secret for oauth2 https://console.developers.google.com/apis/api/drive/overview?pli=1

[vitalif]

As already mentioned in the previous issue:

• drive apis to read/write all files are now restricted
• that means they require some "verification" to give application access to those apis
• however, I think that the verification is useless for opensource apps, because client secret is open to everyone, basically anyone can impersonate grive2
• until the verification is completed it only allows access for 100 users
• in last commits I changed the client id/secret to a newly generated pair. so it worked for 100 users and then it stopped working
• I clicked the "submit for verification" button, so there's nothing more that I cam currently do :-)
• 100 users means that you can use your own client_id/client_secret without the verification

[vitalif]

I don't use cloud storage myself. Because the data in cloud storage isn't yours. The vendor does anything it wants to it

[jfernandoghe]

1. go and blame google. I'm not responsible for the fact that they disable drive APIs for people
2. as a temporary workaround you can register your own client_id + client_secret for oauth2 https://console.developers.google.com/apis/api/drive/overview?pli=1

Mainstream user of Google Drive only with grive... so... any tutorial to set this up? a quick guide? anything quick to follow? Thanks in advanced...

I don't use cloud storage myself. Because the data in cloud storage isn't yours. The vendor does anything it wants to it

Any workaround to set up own 'cloud' storage? really new to the subject as a DIY project... :/

[davama]

got it to work:
#287 (comment)

Keep reading after that post

[wdysun]

I have two google accounts:

a) a free one, I did what it is suggested in #287 (comment), and it works

b) I also have a company account with the full google suite. In that case it doesn't work, google says that grive2 is a not permitted app

[suewonjp]

grive2 works at authentication but it doesn't from then.

20:57:grive$ grive -a --id ****** --secret ******
-----------------------
Please go to this URL and get an authentication code:

https://accounts.google.com/o/oauth2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&redirect_uri=urn:ietf:wg:oauth:2.0:oob&response_type=code&client_id=*********

-----------------------
Please input the authentication code here:
*********
Reading local directories
Reading remote server file list
Synchronizing files
sync "./cvz/bsw.trace.db" changed in remote. downloading
sync "./cvz/bsw.h2.db" changed in remote. downloading
sync "./.gd" created in remote. creating local
sync "./.gd/drivedb" created in remote. creating local
sync "./.gd/credentials.json" created in remote. creating local
Finished!

Works! But when I try to sync after that, it looks like that.

20:58:grive$ grive
Failed to refresh auth token: HTTP 401, body: {
  "error": "unauthorized_client",
  "error_description": "Unauthorized"
}
exception: /build/grive2-RRCxdx/grive2-0.5.2/libgrive/src/protocol/OAuth2.cc(111): Throw in function void gr::OAuth2::Refresh()
Dynamic exception type: boost::exception_detail::clone_impl<gr::OAuth2::AuthFailed>
[gr::expt::BacktraceTag*] = #0 0x559e5366595d grive gr::Exception::Exception()
#1 0x559e5364899d grive gr::OAuth2::AuthFailed::AuthFailed()
#2 0x559e5364861a grive gr::OAuth2::Refresh()
#3 0x559e5364796c grive gr::OAuth2::OAuth2(gr::http::Agent*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
#4 0x559e53602f31 grive Main(int, char**)
#5 0x559e53603ab2 grive main
#6 0x7fd0b4ae1b97 /lib/x86_64-linux-gnu/libc.so.6 __libc_start_main
#7 0x559e5360197a grive _start

@vitalif Well, I think it might be possible that this issue is separate one other than #287

grive version 0.5.2-dev Nov 13 2019 10:41:39

System: Linux Mint 19.2 Cinnamon

---

Oops, sorry. I've figured out I should've done it like so:

grive --id ****** --secret ******

Old habit (just typing grive) won't work any more. Sorry to bother...

[AmonRaNet]

It seems that Google will always block private(free) developer clients as soon as they generate a lot of traffic. And I don't believe that someone will create a commercial account for managing an open source product with many users. The most reliable solution is to create your own client id and use it only for yourself.
Grive already has support for -a -i -e, but that wasn’t enough for me, because you need to specify the identifier and secret each time in the CLI afterwards. Also, it is not backward compatible with many tools and scripts.
In this pull request #294 I made the custom id and secret permanent (also during build).

[vitalif]

Fixed :) grive2 is now verified.