Instapy: wrong login data

[riccardorighettiphoto]

Hello,
I had a "wrong login data" error twice today when running InstaPy. I double cheked the login credentials in my quickstart.py file and they are absolute correct!
Nothing has changed in my installation since about some weeks ago and the script has been working without any issue so far.

Any idea?

FYI I can use my instagram account on mobile or computer and I guess my quickstart is not running in an aggressively manner, see below:

from instapy import InstaPy

insta_username = ''
insta_password = ''

# set headless_browser=True if you want to run InstaPy on a server
try:
    # set these if you're locating the library in the /usr/lib/pythonX.X/ directory
    # Settings.database_location = '/path/to/instapy.db'
    # Settings.browser_location = '/path/to/chromedriver'

    session = InstaPy(username=insta_username,
                      password=insta_password,
                      bypass_suspicious_attempt=True,
                      nogui=True,
                      multi_logs=False)
    session.login()

    # settings
    session.set_lower_follower_count(limit=1000)
    session.set_upper_follower_count(limit=1000000)
    #session.set_do_comment(True, percentage=5)
    #session.set_comments(['awesome', 'cool', 'stunning', 'beautiful'])
    session.set_do_follow(enabled=True, percentage=10, times=1)
    session.unfollow_users (amount=20, onlyInstapyFollowed=True, onlyInstapyMethod='FIFO', sleep_delay=300, onlyNotFollowMe=False, unfollow_after=168*60*60)  #here, will unfollow every single user after following at least 7 days

    # actions
    session.like_by_tags(['motorsportphotography', 'sportphotography', 'racing', 'blancpaingtseries'], amount=100)

finally:
    # end the bot session
    session.end()

[tsirolnik]

Same happened to me

[davidmurdoch]

Same here. Looks like instagram is soft-banning IP addresses. I can only log in to accounts via facebook login on this particular network now. ALL login attempts via username/password return the error message: "The username you entered doesn't belong to an account. Please check your username and try again."

They may be doing some more advanced network/computer fingerprinting as well, as I changed my public IP address, cleared all cookies, and tried a different browser I hadn't used for Instagram before and still couldn't log in with a username/password to any account (but I could via another computer on another network).

[Luisetty]

I did have this issue yesterday, it seems instagram has an issue on logins from tables, phones and pc. also it was a trend (23th March 2018) on twitter about instagram was having issues with logins for many people.

Im still unable to log :(

[riccardorighettiphoto]

I run Instapy on my VPS by crontab and I am still getting a Wrong login data error (I firstly got the error last night at 2:00am).
I have just tried to run InstaPy from a local installation on my notebbok and it works. So I guess it is a limitation related to the VPS IP address, which is a little bit worrying.
I cannot believe why I got soft-banned, as stated before I don't run an aggressive script IMHO.

[sionking]

http://downdetector.com/status/instagram

[sionking]

Anyway we can login from facebook and let chrome use the local chrome profile:
https://stackoverflow.com/questions/34179420/can-i-run-selenium-chromedriver-with-cookies-from-actual-chrome-installation?rq=1

[riccardorighettiphoto]

@sionking
Despite I don't know what you referred by your last message, as I said before, I can run instapy from my notebook but not from my VPS, so I guess my IP has been locked out. Fantastic news... :(

[sionking]

I get the same login error on one of my account, but from local chrome (personal laptop) login using facebook works! so I guess it is not IP issue. at least not for me

[riccardorighettiphoto]

Three days passed and I am still unable to login, really frustrating and I cannot understand why this matter.
I’ve just tried with another account I have and got the same error, so I think my IP is permanently locked out.

[Luisetty]

people from different parts of the world are still having the same issue, some are saying they can login again using a vpn and others are being unable.

I still can't access via pc/tablet but I can use phone.

[riccardorighettiphoto]

Report:
just tried from another VPS and a different IP. Nothing to do with that as well, again a "wrong login data" error!
I cannot understand why but I am starting to be really angry.

[Tjorriemorrie]

@riccardorighettiphoto I understand your frustration! Just to confirm: you can log in normally on the website/app, but the problem is only when using Instapy that it says wrong login data?

[riccardorighettiphoto]

hello @tjorriemorrie
Currently I am able to:

• login to my Instagram profile from computer, mobile and any other device using the app or the browser;
• login to my Instagram by using Instapy running through any computer.

I cannot login to my instagram profile through instapy installed on my (two) VPS.

[CharlesCCC]

I see you have
bypass_suspicious_attempt=True, set, if you alreayd got cookie created, you should set this to False.
In addition, Are you able remote to the VPS server and see what exactly the browser are doing ?

[riccardorighettiphoto]

@CharlesCCC
Hello,
something has changed because now if I set bypass_suspicious_attempt=True (every time) it ask me for the security code sent by email. If I set it False, it returns "wrong login data".
The cookie file is already stored but if I don't set True that setting (bypass_suspicious_attempt) then I get the error.
I cannot understand anything.

P.S.: what did you mean by "... are you able to remote to the VPS server and see..." I usually access to the VPS server by a SSH connection via PuTTY and by the terminal.

[CharlesCCC]

@riccardorighettiphoto leave bypass_suspicious_attempt=True for now, delete your cookie from log folder, and then run the quickstart.py again, make sure you the cookie is recreated and then set bypass_suspicious_attempt=False you should be fine afterwards.

[riccardorighettiphoto]

Hello @CharlesCCC
thanks for you help but unfortunately it does not work. Here below the list of task executed:

1. Removed cookie "*.pkl" file
2. Run quickstart.py with bypass_suspicious_attempt set to True
   Result: the script runs well and it creates the new cookie file.

1. Changed the value to FALSE
   Result: the script does not run and wrong login data appeared.

I cannot understand. The problem here is that I cannot use the script by scheduled task because I have to add every time the security code sent by email. So I have to launch the script manually.
Any idea?

[CharlesCCC]

@riccardorighettiphoto
On your step 2

Run quickstart.py with bypass_suspicious_attempt set to True
Result: the script runs well and it creates the new cookie file.

Did you need get the Verification code ?

when you say this,

add every time the security code sent by email. 

it sounds like your script is not pick up the cookie file. otherwise, it should not ask for Verification code again.

Last thing to try is, download your log folder to your locally and run it on your personal computer.
You will have to observe the behavior from the automated chrome window in order to tell what was going on.

[riccardorighettiphoto]

@CharlesCCC
I cannot understand you.
When I set to TRUE the script creates the cookie file and it requires me the security code.
After this first run, if I set to FALSE and launch the script, the message "Cookie file not found, etc...." comes up (but the file is still there, it is not disappeared) and then returns the wrong login data error.
I cannot run on my notebook because I have different installation of instapy, a different OS etc...

[CharlesCCC]

@riccardorighettiphoto To be honest, i'm out of clue why you keep getting "Cookie file not found, etc...." when there is one. If you can't test it locally, I hope someone with more experiences might able to help you on this matter further.

[mikestan]

I've gotten the Wrong login Data error a few times and the only thing I've been able to do with InstaPy (headless on Raspberry Pi) is to wait 24 hours from the last error. I think it's essentially a soft ban on the IP address so you just have to wait for it to cool down for each login you are using.

[morrigan]

I have this issue for the last few days and it started happening after I changed my username. I tried to set it up on another server today from scratch but same thing.

[Lando-L]

Same here :( If anyone has any news or a fixes for that I would really appreciate any help.

Using bypass_suspicious_login=True runs into Unable to locate email or phone button, maybe bypass_suspicious_login=True isn't needed anymore and the Wrong login data!

[mkhattar]

same issue! works for 1 account only on my laptop

[Lando-L]

My problem was fixed after getting the newest version from the master and follwing #2133 (comment).

[priscila225]

I had the same problem!!! I finally fixed here when I changed the line 174 from login_util.py code to be if len(nav) >= 0 instead len(nav) == 2 --> note: I didn't investigate more this line but I bet this is totally diff than 2 and turns into a false return.

[miguelmsanchezm]

I don't if this will help someone, but what help me was to log in manually from a computer and changing the line 170 from login_util.py from this sleep(5) to this sleep(30). After that the cookie was created and I changed the line back to sleep(5) . Now everything works perfectly 👍

[nikartz]

Thank you, @priscila225 ! Your fix is working for me.
Maybe a PR? Seems like it doesn't interfere with anything else, so it would not hurt if everyone would have this fix implemented. Every now and then someone runs into this issue.

[woavy]

Disabling 2FA worked for me. I discovered this by enabling headless for a minute.