Failed Logins

[martin@rootjazz]

what URL does the browser go to?

Does it open :
https://tumblr.com

or
https://tumblr.com/login

[snibi]

It does open https://www.tumblr.com/.

[martin@rootjazz]

hmmm ok. So there is communication.

the program should open
tumblr.com
then set cookies
then try and open tumblr.com/login

There must be something happening in that first setting of the page and cookies. Let me check that code and get another update for you

[martin@rootjazz]

https://rootjazz.com/tumblingjazz/updatetesting.html

please try the process again
then submit logs


HELP > LOGS > SUBMIT

then send your logs ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)

[snibi]

Thanks for the update. The logs id: logs_27386.

Edit: after scrape stats on a new instance with same accs where no cookies exists, some accounts appeared as "failed login".
when i try a browser login it stops execution at "data:," part instantly no logs written.
i can by hand enter tumblr.com, or check ip all is working.

[martin@rootjazz]

thanks, got some more logs. Seems to be a known issue with chromedriver / selenium.

There seems to be some updates for both projects. So I will include them for the next update and let you know when ready

[martin@rootjazz]

bit of a delay. The updated dlls breaks selenium for me now

[martin@rootjazz]

https://rootjazz.com/tumblingjazz/updatetesting.html

please try this. Seems that if the page times out, it loses the connection with the browser (it shouldn't but appears to) so have increased timeouts to avoid that. If you have a SLOW connection, it might still not be enough. But as long as tumblr.com home page loads within 5 minutes you should be fine...

[snibi]

Many thanks for the fast update, unfortunately it does the same thing with a new information at the top on chrome:



just 1 second after the browserwindow opens, i get "An error occured, it has been logged, if persists, submit logs to support and let them know:"

logs_68574.

[martin@rootjazz]

maybe there are build issues with the new dlls, testing now on a different machine