[GH-ISSUE #72] Error=BadAuthentication #66

Closed
opened 2026-02-25 20:34:34 +03:00 by kerem · 14 comments
Owner

Originally created by @limsifu on GitHub (Oct 19, 2020).
Original GitHub issue: https://github.com/B16f00t/whapa/issues/72

Requesting Auth for Google....
Failed

Error=BadAuthentication

Workaround

  1. Check that your email and password are correct, if so change your google password and try again.
  2. Your are using a old python version. Works > 3.7.7.
  3. Update the gpsoauth dependency to its latest version, use in a terminal: 'pip install -U gpsoauth' or 'pip3 install -U gpsoauth'
    settings.cfg
    [report]
    logo = ./cfg/logo.png
    company =
    record =
    unit =
    examiner =
    notes =

[auth]
gmail = xxx@gmail.com
passw = xxx
celnumbr = xxx

User and Password is correct.

Originally created by @limsifu on GitHub (Oct 19, 2020). Original GitHub issue: https://github.com/B16f00t/whapa/issues/72 Requesting Auth for Google.... Failed Error=BadAuthentication Workaround ----------------- 1. Check that your email and password are correct, if so change your google password and try again. 2. Your are using a old python version. Works > 3.7.7. 3. Update the gpsoauth dependency to its latest version, use in a terminal: 'pip install -U gpsoauth' or 'pip3 install -U gpsoauth' settings.cfg [report] logo = ./cfg/logo.png company = record = unit = examiner = notes = [auth] gmail = xxx@gmail.com passw = xxx celnumbr = xxx User and Password is correct.
kerem closed this issue 2026-02-25 20:34:34 +03:00
Author
Owner

@B16f00t commented on GitHub (Oct 25, 2020):

Are you using the latest version of whapa?

<!-- gh-comment-id:716112268 --> @B16f00t commented on GitHub (Oct 25, 2020): Are you using the latest version of whapa?
Author
Owner

@faliagag commented on GitHub (Nov 12, 2020):

It happens to me exactly the same.
I am with version whapa 1.21, phyton 3.7.7.
Update gpsoauth
And still I get Error = BadAuthentication

<!-- gh-comment-id:726286564 --> @faliagag commented on GitHub (Nov 12, 2020): It happens to me exactly the same. I am with version whapa 1.21, phyton 3.7.7. Update gpsoauth And still I get Error = BadAuthentication
Author
Owner

@inimaginablexhs commented on GitHub (Nov 22, 2020):

i have the same problem :c

<!-- gh-comment-id:731849376 --> @inimaginablexhs commented on GitHub (Nov 22, 2020): i have the same problem :c
Author
Owner

@molossusbook commented on GitHub (Nov 22, 2020):

Hi: sounds like a great tool but cannot get it to work, because I get same problem with "BadAuthentication"
Last version of whapa (updated today) and python, under lubuntu18.
Email and password checked and correct. Tried to change password but does not solve.
I wonder if there is anything I have to do on the Google side: any account setting? any unlocking?
visited https://accounts.google.com/DisplayUnlockCaptcha and unlocked access there.
Just let me know if you need me to produce other info to let you reproduce and/or understand the issue
thanks a lot

<!-- gh-comment-id:731868041 --> @molossusbook commented on GitHub (Nov 22, 2020): Hi: sounds like a great tool but cannot get it to work, because I get same problem with "**BadAuthentication**" Last version of whapa (updated today) and python, under lubuntu18. Email and password checked and correct. Tried to change password but does not solve. I wonder if there is anything I have to do on the Google side: any account setting? any unlocking? visited https://accounts.google.com/DisplayUnlockCaptcha and unlocked access there. Just let me know if you need me to produce other info to let you reproduce and/or understand the issue thanks a lot
Author
Owner

@B16f00t commented on GitHub (Nov 23, 2020):

There is a problem with the latest version of requests.
I recommend install requests 2.21 to solve it.

Sent from my iPhone

On 22 Nov 2020, at 22:23, inimaginablexhs notifications@github.com wrote:


i have the same problem :c


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

<!-- gh-comment-id:732044445 --> @B16f00t commented on GitHub (Nov 23, 2020): There is a problem with the latest version of requests. I recommend install requests 2.21 to solve it. Sent from my iPhone > On 22 Nov 2020, at 22:23, inimaginablexhs <notifications@github.com> wrote: > >  > i have the same problem :c > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or unsubscribe.
Author
Owner

@inimaginablexhs commented on GitHub (Nov 23, 2020):

install the request 2.21 and I continue with the problem :c

<!-- gh-comment-id:732057301 --> @inimaginablexhs commented on GitHub (Nov 23, 2020): install the request 2.21 and I continue with the problem :c
Author
Owner

@sobelito commented on GitHub (Nov 23, 2020):

In using whagodri.py, I have seen an interesting behavior where it looks like these calls are failing w/ "BadAuthentication" if run from VMWare or from an EC2 instances, but they work from Windows Desktop and OSX.

In looking at the "Recent security activity" and clicking on the individual event, I can see "VMWare Virtual Platform" or "t3.medium" respectively on the failed attempts. Anyway, just wanted to share the data points.

I also tested from Windows Desktop but VPNing through an EC2 IP address, and this worked.

<!-- gh-comment-id:732305197 --> @sobelito commented on GitHub (Nov 23, 2020): In using whagodri.py, I have seen an interesting behavior where it looks like these calls are failing w/ "BadAuthentication" if run from VMWare or from an EC2 instances, but they work from Windows Desktop and OSX. In looking at the ["Recent security activity"](https://myaccount.google.com/u/0/notifications?origin%3D3&origin=3) and clicking on the individual event, I can see "VMWare Virtual Platform" or "t3.medium" respectively on the failed attempts. Anyway, just wanted to share the data points. I also tested from Windows Desktop but VPNing through an EC2 IP address, and this worked.
Author
Owner

@sobelito commented on GitHub (Nov 23, 2020):

There is a problem with the latest version of requests. I recommend install requests 2.21 to solve it.

Sent from my iPhone
On 22 Nov 2020, at 22:23, inimaginablexhs @.***> wrote:  i have the same problem :c — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you! Indeed, did "pip install requests==2.21.0" on the EC2 instance (as noted above) and it worked.

<!-- gh-comment-id:732319203 --> @sobelito commented on GitHub (Nov 23, 2020): > There is a problem with the latest version of requests. I recommend install requests 2.21 to solve it. > […](#) > Sent from my iPhone > On 22 Nov 2020, at 22:23, inimaginablexhs ***@***.***> wrote:  i have the same problem :c — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Thank you! Indeed, did "pip install requests==2.21.0" on the EC2 instance (as noted above) and it worked.
Author
Owner

@molossusbook commented on GitHub (Nov 23, 2020):

installed requests 2.21.0 and IT DID WORK for me, and that is the good news

just to make sure, here below is the output I get when checking a whatsapp backup
do you confirm this indicates an empty/corrupt backup? (that would be the bad part of the news)

thank you all for the support

**-------------- Whatsapp Google Drive Extractor --------------
[i] Searching...

Requesting Auth for Google....
Granted

Getting Token from Google....
Granted

No files for this backup**

<!-- gh-comment-id:732438199 --> @molossusbook commented on GitHub (Nov 23, 2020): installed requests 2.21.0 and IT DID WORK for me, and that is the good news just to make sure, here below is the output I get when checking a whatsapp backup do you confirm this indicates an empty/corrupt backup? (that would be the bad part of the news) thank you all for the support **-------------- Whatsapp Google Drive Extractor -------------- [i] Searching... Requesting Auth for Google.... Granted Getting Token from Google.... Granted No files for this backup**
Author
Owner

@B16f00t commented on GitHub (Nov 24, 2020):

It seems that the google drive account linked to the phone does not have any backup. So it may be a bad backup or one that never existed.

<!-- gh-comment-id:733102538 --> @B16f00t commented on GitHub (Nov 24, 2020): It seems that the google drive account linked to the phone does not have any backup. So it may be a bad backup or one that never existed.
Author
Owner

@suttter commented on GitHub (Nov 24, 2020):

Problem solved after installing 2.21.0.

I got the msgstore.db.crypt12 file but the key is needed to decrypt it. Is it possible to get the msgstore.db file or the key from Drive?

<!-- gh-comment-id:733219176 --> @suttter commented on GitHub (Nov 24, 2020): Problem solved after installing 2.21.0. I got the msgstore.db.crypt12 file but the key is needed to decrypt it. Is it possible to get the msgstore.db file or the key from Drive?
Author
Owner

@molossusbook commented on GitHub (Nov 24, 2020):

ok. will also double check by creating another (valid) backup and trying with that
thanks!

<!-- gh-comment-id:733280890 --> @molossusbook commented on GitHub (Nov 24, 2020): ok. will also double check by creating another (valid) backup and trying with that thanks!
Author
Owner

@shamanasanka commented on GitHub (Nov 26, 2020):

Hi,

I'm getting this error, what should i do?

File "E:\whapa-master\libs\whagodri.py", line 296, in
getConfigs()
File "E:\whapa-master\libs\whagodri.py", line 64, in getConfigs
except(ConfigParser.NoSectionError, ConfigParser.NoOptionError):
AttributeError: type object 'ConfigParser' has no attribute 'NoSectionError'

Thanks

<!-- gh-comment-id:734070008 --> @shamanasanka commented on GitHub (Nov 26, 2020): Hi, I'm getting this error, what should i do? File "E:\whapa-master\libs\whagodri.py", line 296, in getConfigs() File "E:\whapa-master\libs\whagodri.py", line 64, in getConfigs except(ConfigParser.NoSectionError, ConfigParser.NoOptionError): AttributeError: type object 'ConfigParser' has no attribute 'NoSectionError' Thanks
Author
Owner

@Samour50 commented on GitHub (Dec 5, 2020):

Are you using the latest version of whapa?

Yes

<!-- gh-comment-id:739317511 --> @Samour50 commented on GitHub (Dec 5, 2020): > Are you using the latest version of whapa? Yes
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/whapa#66
No description provided.