CODEWITHSUNDEEP
google-chromeseleniumselenium-chromedriver
Anton
Anton

Reputation: 940

Chrome 58 Not secure Data in URL

The recent upgrade to Chrome 58 has caused an issue. When Selenium launches an instance of Chrome it doesn't navigate to the initial URL like it did with Chrome 57. Now when Chrome is launched via Selenium we get this issue:

ChromeNotSecureData

It just hangs right there and won't move. Has anyone else found a workaround for this?

If I downgrade back to Chrome 57... no issues what-so-ever! Unfortunately we need to use 58 now.

I have several nodes in my grid and this occurs on every single one of them. I thought maybe it was a group policy or something but the fact that it runs perfectly on 57 makes no sense to me.

** Update: another issue that I'm having is that it often takes two or three attempts at opening the browser before it finally launches.

Upvotes: 3

Views: 1668

Answers (1)

Impally
Impally

Reputation: 31

Add the --enable-automation argument to your webdriver. By default, Chrome 58 requires https and it will not display pages that cannot handle this, the enable-automation lets the browser know the webdriver is steering and it is safe to display the page.

Upvotes: 3

Related Questions