New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong login data - Current configuration has issues with newest Chrome v62 on docker #852

Open
Radzam opened this Issue Nov 2, 2017 · 19 comments

Comments

Projects
None yet
8 participants
@Radzam

Radzam commented Nov 2, 2017

I have made a clean install of InstaPy and made some tests using docker microservices. I didnt have any issues with the old version that used previous chrome versions. Now with a clean install even if I updated the chrome driver to latest version (2.33) and even tried rebuilding the images, it is telling me that in most cases the login data is wrong and just closes the session. It is not and I can see it login correctly when VNC only to close the chrome window after that. It sometimes goes through and works just fine.

web_1       | Wrong login data!
selenium    | 10:44:55.911 INFO - Found handler: org.openqa.selenium.remote.server...
@pilotdude

This comment has been minimized.

pilotdude commented Nov 2, 2017

I've seen this issue occurring on previous versions of InstaPy as well, at somewhat random times. For me sometimes it goes through and sometimes it doesn't. Usually if I restart InstaPy it works fine.

@converge converge added the help wanted label Nov 2, 2017

@Radzam

This comment has been minimized.

Radzam commented Nov 2, 2017

@pilotdude Thanks. It is very annoying. Do you know what causes it and did you find a solution for it?

@pilotdude

This comment has been minimized.

pilotdude commented Nov 2, 2017

Nope, no idea what is happening or why. Potentially related: is it normal for chrome to open two tabs on initialization? One for Instagram and one looking like this:
image

@mojoego

This comment has been minimized.

mojoego commented Nov 4, 2017

Same same here on both my macbook and an fresh amazon E2 instance... any clue?

@Radzam

This comment has been minimized.

Radzam commented Nov 4, 2017

Seems like a lot of people experience this issue, could you please take a look at it? @timgrossmann @converge

@converge

This comment has been minimized.

Collaborator

converge commented Nov 4, 2017

just tested it in Chrome v62, it's ok. Unfortunately I don't have docker here at the moment to test it.

@Radzam

This comment has been minimized.

Radzam commented Nov 4, 2017

@converge I think the issue happens to all of us using docker. Do you have any clue what it might be?

@timgrossmann

This comment has been minimized.

Owner

timgrossmann commented Nov 4, 2017

@mojoego @Radzam The problem is that Instagram blocks you from logging in to your accounts...

The same happens sometimes when using it with a DigitalOcean server for the first time.
In that case, the IP does not change after the first time, I think with docker it's a little bit different (Docker people correct me if I'm wrong, please)...

This means that if you log in to your account with your local machine (simply do it with the webpage), and then start the script (with docker), you should see a notification at one point that there was a "suspicious" login attempt.
If you approve that as legit, then it should not ask you again (at least with DO it's that way)

Can any of you get what I say?

@mojoego

This comment has been minimized.

mojoego commented Nov 4, 2017

Thanks for you answer, for your work!
The thing is I use docker on my laptop too... and I get the same error message even though I can login to instagram from any browser on the same mac without any message...

@Radzam

This comment has been minimized.

Radzam commented Nov 5, 2017

@timgrossmann Thanks for answering but I dont think this is the case here. When using VNC I can actually see it login and start navigating on tags before it closes down and says that it's wrong login. So there is def some bugg when using the current docker setup, perhaps there is compatibility issues with the configured driver and selenium version? How would I do to switch to firefox with docker microservice setup?

@converge

This comment has been minimized.

Collaborator

converge commented Nov 5, 2017

This happened to me while I was working in Windows, I added this line, and looks like it fixed, can anyone test it ?

sleep(1)

after input_username =

if this is a fix, we could use selenium wait()

@mojoego

This comment has been minimized.

mojoego commented Nov 6, 2017

In the login script, I tried the

wait()

as you wrote: same error.

Then I then tried to change :

if len(nav) == 1: return True else: return False

It seems to connect, the scripts starts, but nothing is liked or anything. Note that my IP is not blacklisted and my account is not ghosted...

@converge

This comment has been minimized.

Collaborator

converge commented Nov 6, 2017

@mojoego tha'ts nice! I think we are almost there. What I really think will solve this issue is understand what InstaPy is doing wrong, I wish I had a scenario where it always happens so we could debug it.

Is there anyone with this issue that could give me remote access to it ? So I can debug it (I'm at Slack)

@pigipi

This comment has been minimized.

pigipi commented Nov 9, 2017

I have the same problem on my mac and I use also Docker.

The script begins, and after connection it stops/crashes after login (I can see 'Wrong login data!' in the terminal, then it closes the session 'Session ended').

Sometimes it works, sometimes it doesn't. Unfortunately, and generally, it doesn't work...

@mojoego

This comment has been minimized.

mojoego commented Nov 9, 2017

Personally I move yesterday to a virtual machine to test with Ubuntu, it works flawlessly, so I just bought a Raspberry Pi 3 to install it on...
Best move ever I think... so easier.

@pigipi

This comment has been minimized.

pigipi commented Nov 9, 2017

In my case when I add wait(), it doesn't crash. But the script waits indefinitely.
I'll do it without docker.

@hestuppfodarn

This comment has been minimized.

hestuppfodarn commented Nov 9, 2017

I found a personal solution for my case. I downloaded the new chromedriver, now everything works frictionless.

@pigipi

This comment has been minimized.

pigipi commented Nov 15, 2017

I did the update but no change on my case. So I don't use Docker.

@tuxity

This comment has been minimized.

tuxity commented Nov 17, 2017

When I print the source code I can see I'm still on login page with the error message
The username you entered doesn't belong to an account. Please check your username and try again.
The form seems to be correctly fill with my username and password
I'm sure of my creds, I've updated everything, I don't run it with docker just python3 quickstart.py directly into terminal

Changing to if len(nav) == 1: is a bad idea because the script runs but you aren't connected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment