ERROR: ('invalid_grant: Bad Request'

[Steve Gayner]

GYB Windows 10 version 1909

Haven't run GYB for over a year. Successful many times during that time frame. 

Used the command I always use to get mail by year. Got a failure.

Found updated version. Unzipped into existing directory.

Same failure:  

Command: e:\GMail GYB Backup>gyb --email xxxx...@gmail.com --search "before:2020 after:2018"  [where xxxx.yyyy is my valid gmail userid, used before for GYB]

Error:

ERROR: ('invalid_grant: Bad Request', '{\n  "error": "invalid_grant",\n  "error_description": "Bad Request"\n}')

I have no idea what to do. Tried searching for parts of that error message, but I usually wind up in a Python thread.

Any pointers? 

TIA.

Steve

[Jay Lee]

Run

gyb --action revoke --email x...@gmail.com

this will revoke the old authorization (which was likely removed from your account when you reset your password or removed it). Then re-run your command, you'll be walked back through authorization and then it should work.

Jay Lee

--
--
You received this message because you are subscribed to the Google
Groups "Got Your Back: Gmail Backup" group.
To post to this group, send email to got-yo...@googlegroups.com
To unsubscribe from this group, send email to
got-your-bac...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/got-your-back?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Got Your Back: Gmail Backup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to got-your-bac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/got-your-back/e2a337e3-e659-41a2-8347-a139b627025fo%40googlegroups.com.

[Steve Gayner]

Thank you for your input. I tried that:

e:\GMail GYB Backup>gyb --action revoke --email xxxx...@gmail.com

results in:

ERROR: ('invalid_grant: Bad Request', '{\n  "error": "invalid_grant",\n  "error_description": "Bad Request"\n}')

Is there a manual way I can revoke?

[Brett Carver]

I started getting this problem yesterday.  I have 4 accounts I'm backing up.

1.  G Suite legacy - works fine

2.  Gmail

ERROR: ('invalid_grant: Bad Request', '{\n  "error": "invalid_grant",\n  "error_description": "Bad Request"\n}')

3, and 4.  Gmail

ERROR: ('invalid_grant: Token has been expired or revoked.', '{\n  "error": "invalid_grant",\n  "error_description": "Token has been expired or revoked."\n}')

Doing the --action revoke has no effect and generates the same errors as above.

[Jay Lee]

You can just delete the .cfg file named after the email address and then reauth.

Jay

--

--
You received this message because you are subscribed to the Google
Groups "Got Your Back: Gmail Backup" group.
To post to this group, send email to got-yo...@googlegroups.com
To unsubscribe from this group, send email to
got-your-bac...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/got-your-back?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Got Your Back: Gmail Backup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to got-your-bac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/got-your-back/19726041-1f4c-4ef2-a55d-0d50c9ab9aedo%40googlegroups.com.

[E]

Same issue started about 3am UTZ this morning here.

ERROR: ('invalid_grant: Token has been expired or revoked.', '{\n  "error":

        "invalid_grant",\n  "error_description": "Token has been expired or revoke

       d."\n}')

[Brett Carver]

You can just delete the .cfg file named after the email address and then reauth.

That worked.  I bit of a PitA - lots of clicking and copy/pasting.   I hope whatever happened to break all the accounts doesn't happen often.

[E]

Same

[Steve Adeff]

I'm having this issue too, but not sure where this .cfg file is, I have two sqlite files.

[Matthew Lancey]

Found this conversation via a Google search for the "bad request" error, which I started seeing a few days ago. This reply is aimed at anyone else who arrives here for the same reason!

1. The .cfg file, for me, was in the same folder that I run gyb from. Having said that, I'm on a Mac, so Windows users might have a different experience
2. The resolution for the problem was indeed to just remove the .cfg file - actually I just changed the extension to .cfg.bak instead - and re-running the gyb command I usually run for an incremental backup.

In doing this I expected to have to go through the full long-winded (re-)auth process with Google, but actually all I needed to do was paste the first short link gyb provided; re-authenticate my Google account in the browser; then copy/paste the verification code provided by Google back into gyb. After that, gyb launched straight into its usual process for syncing my email. Easy!

[Simon Crosland]

I am now seeing this error every 7 days and to recover I have to delete the .cfg file and go through the quick re-authentication process described in the previous message.

I am using gyb with a consumer @gmail account and a Google Workspace domain. The @gmail.com account is used as the service account for the Google Workspace domain so that I only have to have one installation of gyb. 

The error occurs when running gyb to back up the @gmail.com account, but never affects the Google Workspace even after the @gmail.com account is in the error state and will not itself complete a backup. When the error happens gyb exits with status 18.

A redacted snippet from my logging:

/Users/***/bin/gyb/gyb --email "***@gmail.com" --local-folder "/Volumes/Data One/Backups/Gmail/***" --action backup

ERROR: ('invalid_grant: Token has been expired or revoked.', {'error': 'invalid_grant', 'error_description': 'Token has been expired or revoked.'})

Return code: 18
Stdout: None
Stderr: None

I'd be happy to try to help debug this problem. I'm wondering if I'll have to end up with two gyb installations, one for the @gmail.com account and one for the Google Workspace domain?

Cheers,

Simon

[Tony Scelfo]

I also get the "ERROR: ('invalid_grant: Token has been expired or revoked.', {'error': 'invalid_grant', 'error_description': 'Token has been expired or revoked.'})" errors often. Deleting the .cfg and re-authenticating fixes everything for about a week until it fails again. I don't fix it every time it happens so I can't confirm the same 7 day pattern but that seems about right based on the times I have gone to reauthenticate.

--

--
You received this message because you are subscribed to the Google
Groups "Got Your Back: Gmail Backup" group.
To post to this group, send email to got-yo...@googlegroups.com
To unsubscribe from this group, send email to
got-your-bac...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/got-your-back?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Got Your Back: Gmail Backup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to got-your-bac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/got-your-back/3215cb79-524a-4fe1-abe3-23999c79b5fen%40googlegroups.com.

[Ketan Vijayvargiya]

I started using GYB and am running into the same problem: "I am now seeing this error every 7 days and to recover I have to delete the .cfg file and go through the quick re-authentication process described in the previous message."

I use a regular/consumer Gmail address, not related to Google Workspace.

I setup a daily cron to backup my Gmail account and it stopped working after a week.

Any ideas on how I can fix this in a permanent way?

[Jay Lee]

This is unfortunately expected behavior. Google revoked the token on projects in "test" mode every 7 days. I'm not aware of a workaround for consumer accounts.

Jay

To view this discussion on the web visit https://groups.google.com/d/msgid/got-your-back/e9ea6e24-118a-4fc7-8f45-2031879ab248n%40googlegroups.com.

[Dylan Gordon]

This is getting beyond my expertise, but is it possible using another OAuth flow might work? The gmvault people are talking about migrating to the loopback flow. See:

https://github.com/gaubert/gmvault/issues/361#issuecomment-1207824886

and

https://developers.google.com/identity/protocols/oauth2/resources/loopback-migration

Is there some way I can config GYB to do this?

Dylan

[Dylan Gordon]

Just saw this:

"It seems that there is a way to circumvent the 7 days expiration for the refresh token. You have to publish the application and then skip sending any verification details. Just clicking the publish button and creating a new refresh token is enough (sometimes you need to recreate again after 7 days in order for it to work)."

https://github.com/guillaumeaubert/gmvault-docker/issues/2#issuecomment-938706222

When I hit publish on my GYB app it told me I don't even need to send verification details so we'll see if this works..

Dylan

[Jay Lee]

GYB is already using the loopback flow as of the March 1.60 release. The 7 day token revoke issue is a separate behavior of unpublished projects.

Jay

To view this discussion on the web visit https://groups.google.com/d/msgid/got-your-back/24cf38c4-4848-44ed-9867-a6a64f3a6457n%40googlegroups.com.

[Dylan Gordon]

Well, the refresh token created after publishing the application is still valid 9 days later.

Can anyone tell me what the risks of having this be a public external app in my non-Workspace account are? 

If nothing dire, I might suggest editing https://github.com/GAM-team/got-your-back/wiki#general under "Important note:" to suggest publishing the project vs. having it read "you probably want to avoid that option" as it does right now.

Either way, probably still worth letting people know in this section that their refresh token will expire in 7 days. My own bad for not testing before now but I went a solid year+ assuming this was working when it worked for less than a week!