-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Sign in with Google temporarily disabled for this app #520
Comments
facing same error. |
Same error. |
Duplicate #506 |
Hello, see my comment on #514 : #514 (comment) |
Same error. |
Thank you, It Worked for me; |
Is there another solution, my Beaglebone Black is low on space and this solution takes up too much space. |
I went on and used |
I'm a G Suite user, I've been able to get past that error by whitelisting GDrive on the Admin Console https://admin.google.com/AdminHome?hl=en#Oauth2ScopeManagement:subtab=trusted Now I get a different error
which is apparently related to the GO client library for Google googleapis/google-cloud-go#1350 (comment) All of this may be related to this changes by Google: https://support.google.com/a/answer/7281227?hl=en The problem seems to be present with other programs using Google APIs |
Same problem. Worked about a month ago, installed gdrive on a new computer this morning and got the Verification error listed by op. Will try building from source next. |
I was able to do a workaround on a new system by copying the contents of .gdrive from an older system where I had it set up to the new machine. |
Same error here |
move to RClone project, GDrive Crossed the Jordan, it's dead 💀 |
Try to use my script to build gdrive with your own Google credential: https://github.com/mbrother2/backuptogoogle |
I have an older gdrive version on my ubuntu, it is working. But the new one - not. What is the problem? Why the old one is confirmed by Google, but the new one not? Does it happen to all Google accounts or only to some specific? Any chance to solve the problem? |
Hello Everyone, I've written a way to fix the issue. Please check this article: Mount Google Drive using GDrive on Linux Server with Own OAuth Credentials. I hope this method will work on all servers. Thanks. |
No need to compile from source, just create service account in google console and use |
I get this error when i follow login link
The text was updated successfully, but these errors were encountered: