-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Description
So, this is the issue: (I've changed the burner account username to ****** for privacy)
Attempt to login...
ClientError bad_password (Code: 400, Response: {"message": "We can send you an email to help you get back into your account.", "status": "fail", "error_title": "Forgotten password for *", "buttons": [{"title": "Send email", "action": "send_one_click_login_email"}, {"title": "Try again", "action": "dismiss"}], "is_cp_nonce_flow": false, "login_identifer_type": "username", "login_user_input": "", "qe_device_id": "k2d6247ab-1b96-10o1-6y98-213k70fb9kkl", "login_attempt_count": 1, "login_source": "unknown", "error_code": 1, "invalid_credentials": true, "exception_name": "UserInvalidCredentials", "retry_response": null, "error_type": "bad_password"})We can send you an email to help you get back into your account.: bad_password
Ok folks so I'm going to discuss the methods I used to bypass this issue, obviously none of them worked out but I'm telling you all to not waste time on it:
1. Tried the session id by logging into my account on Instagram web and copy pasted the session id into the folder config>setting.json as:
{ "session_id"="uaefheuhfewuhewuhgehrgeorgherweafaeugh"
}
this didn't work
2. I made an account on HickerAPI as they give 100 free tokens for new accounts, I copy pasted the hikerapi_token in config txt file along with username and password like this:
[Credentials]
username =random123 //example username, not real
password =random@123 //example password not real lol
hikerapi_token =afh2uh3h425hh29a923s93rf9a3rh249afu3bhb1 //random characters typed to showcase api lol
the earlier script aka V1 of osintgram was successfully connecting to hikerapi token but in V2 it didn't even get to that point which is disappointing as it was supposed to be at least working for V2 ....
3. I deleted everything in setting.json in config folder and replaced with {} only so to tell the system I've no cookies yet and I want to start fresh, but this didn't work out either
Advice: Don't try logging in using different burner account as there is a possibility that Instagram must've flagged out current log in attempts as "bot login attempt", It doesn't recognize us as a human but a bot or say python script so there is great chance that Instagram will block our IP address temporarily or permanently (depending on the desperation of log in attempts) as a protective measure.