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

Firefox 47 - Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. #2110

Closed
mmwwipula opened this Issue May 16, 2016 · 16 comments

Comments

Projects
None yet
9 participants
@mmwwipula

mmwwipula commented May 16, 2016

Meta -

OS: Windows 7

Selenium Version: 2.52.0

Browser: Firefox

Browser Version: 47.0b5

Expected Behavior -

Open Browser -> Maximize Window -> Go to Website

Actual Behavior -

Open Bwoeser -> Exception Message='Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms.

Additional Information -

Running NUnit Tests using Selenium Grid. Issue cannot reproduce with Firefox 46 or previous versions.

@jleyba jleyba added the D-firefox label May 24, 2016

@adrianer

This comment has been minimized.

Show comment
Hide comment
@adrianer

adrianer Jun 3, 2016

The same thing happens with Selenium Version: 2.53.0

When watching the behavior live, then one can see that Firefox hangs right after it is opened by Selenium (the Fx GUI can be seen).

adrianer commented Jun 3, 2016

The same thing happens with Selenium Version: 2.53.0

When watching the behavior live, then one can see that Firefox hangs right after it is opened by Selenium (the Fx GUI can be seen).

@davehunt

This comment has been minimized.

Show comment
Hide comment
@davehunt

davehunt Jun 3, 2016

Contributor

You will need to use the new Firefox driver from version 47 onwards. See https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette/WebDriver for details.

Contributor

davehunt commented Jun 3, 2016

You will need to use the new Firefox driver from version 47 onwards. See https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette/WebDriver for details.

@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Jun 3, 2016

@davehunt

This comment has been minimized.

Show comment
Hide comment
@davehunt

davehunt Jun 6, 2016

Contributor

The add-ons signing feature of Firefox has now been pushed to version 48, so when 47 is released it should still be supported. I'm going to unlock this issue to allow users to report if they are still seeing problems after Firefox 47 is released.

Contributor

davehunt commented Jun 6, 2016

The add-ons signing feature of Firefox has now been pushed to version 48, so when 47 is released it should still be supported. I'm going to unlock this issue to allow users to report if they are still seeing problems after Firefox 47 is released.

@SeleniumHQ SeleniumHQ unlocked this conversation Jun 6, 2016

@omeravni78

This comment has been minimized.

Show comment
Hide comment
@omeravni78

omeravni78 Jun 7, 2016

hi all
it happened to me also.
Selenium 2.50.1.0
ff 47
win 7 64 bit

omeravni78 commented Jun 7, 2016

hi all
it happened to me also.
Selenium 2.50.1.0
ff 47
win 7 64 bit

@davehunt

This comment has been minimized.

Show comment
Hide comment
@davehunt

davehunt Jun 7, 2016

Contributor

Firefox 47 has not been released yet (it should be out later today). Please refrain from commenting unless you are using the official release of Firefox 47, preferably with the latest version of Selenium (2.53).

Contributor

davehunt commented Jun 7, 2016

Firefox 47 has not been released yet (it should be out later today). Please refrain from commenting unless you are using the official release of Firefox 47, preferably with the latest version of Selenium (2.53).

@adrianer

This comment has been minimized.

Show comment
Hide comment
@adrianer

adrianer Jun 7, 2016

Firefox 47 has not been released yet (it should be out later today). Please refrain from commenting unless you are using the official release of Firefox 47, preferably with the latest version of Selenium (2.53).

I'm using the Fx 47 build that will most likely be declared today as the official one (from here: https://ftp.mozilla.org/pub/firefox/releases/47.0/ ) - and still experiencing the issue here, so it seems the addon signing hasn't been pushed to 48...

adrianer commented Jun 7, 2016

Firefox 47 has not been released yet (it should be out later today). Please refrain from commenting unless you are using the official release of Firefox 47, preferably with the latest version of Selenium (2.53).

I'm using the Fx 47 build that will most likely be declared today as the official one (from here: https://ftp.mozilla.org/pub/firefox/releases/47.0/ ) - and still experiencing the issue here, so it seems the addon signing hasn't been pushed to 48...

@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester

AutomatedTester Jun 7, 2016

Member

This issue has nothing to do with addon signing. Something in FirefoxDriver is causing Firefox to have a startup crash.

Member

AutomatedTester commented Jun 7, 2016

This issue has nothing to do with addon signing. Something in FirefoxDriver is causing Firefox to have a startup crash.

@pravinrmali

This comment has been minimized.

Show comment
Hide comment
@pravinrmali

pravinrmali Jun 7, 2016

I'm Using Firefox 47 and Selenium-Webdriver 2.53.0 and still experiencing the issue mentioned above.

pravinrmali commented Jun 7, 2016

I'm Using Firefox 47 and Selenium-Webdriver 2.53.0 and still experiencing the issue mentioned above.

@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Jun 7, 2016

@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester

AutomatedTester Jun 7, 2016

Member

Locking this issue to prevent "me too" comments. Please use the subscribe feature to on the right to follow this bug.

Member

AutomatedTester commented Jun 7, 2016

Locking this issue to prevent "me too" comments. Please use the subscribe feature to on the right to follow this bug.

@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester
Member

AutomatedTester commented Jun 7, 2016

We appear to be ticking something in the JSRuntime https://gist.github.com/AutomatedTester/8c011e194e6343b6d9bfbda80af76402

@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester

AutomatedTester Jun 7, 2016

Member

The issue is that code to support cert override was changed in a way that broke Selenium which in turn then crashed Firefox. There is a fix in the works from Mozilla.

As a work around you can either revert to Firefox 46 or you can use Marionette*. We have documented how to get set up with Marionette on MDN.

  • Note : When Extension Signing ships in Firefox 48 or later the current Selenium WebDriver addon approach will no longer work and you will need to update to Marionette.
Member

AutomatedTester commented Jun 7, 2016

The issue is that code to support cert override was changed in a way that broke Selenium which in turn then crashed Firefox. There is a fix in the works from Mozilla.

As a work around you can either revert to Firefox 46 or you can use Marionette*. We have documented how to get set up with Marionette on MDN.

  • Note : When Extension Signing ships in Firefox 48 or later the current Selenium WebDriver addon approach will no longer work and you will need to update to Marionette.
@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester

AutomatedTester Jun 8, 2016

Member

Looks like this patch, once verified, may only be out next week. I strongly suggest people move over to Marionette or downgrade to Firefox 46/ESR 45.

Member

AutomatedTester commented Jun 8, 2016

Looks like this patch, once verified, may only be out next week. I strongly suggest people move over to Marionette or downgrade to Firefox 46/ESR 45.

@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester

AutomatedTester Jun 8, 2016

Member

This has been fixed in Firefox, will close this bug when it is released

Member

AutomatedTester commented Jun 8, 2016

This has been fixed in Firefox, will close this bug when it is released

@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester

AutomatedTester Jun 28, 2016

Member

Firefox 47.0.1 has been released with a fix. We now need to release client libraries to pick up a version bump in the xpi that is used by FirefoxDriver

Member

AutomatedTester commented Jun 28, 2016

Firefox 47.0.1 has been released with a fix. We now need to release client libraries to pick up a version bump in the xpi that is used by FirefoxDriver

@AutomatedTester

This comment has been minimized.

Show comment
Hide comment
@AutomatedTester

AutomatedTester Jun 30, 2016

Member

Most, if not all, of the clients have been released by now

Member

AutomatedTester commented Jun 30, 2016

Most, if not all, of the clients have been released by now

@lukeis

This comment has been minimized.

Show comment
Hide comment
@lukeis

lukeis Jun 30, 2016

Member

it's also now in maven central

Member

lukeis commented Jun 30, 2016

it's also now in maven central

fredj pushed a commit to fredj/polymer-starter-kit that referenced this issue Apr 12, 2018

Set firefox to latest for travis (#928)
* Set firefox to latest for travis

as Selenium - Firefox issue is now fixed SeleniumHQ/selenium#2110.

* Remove single quotes

Travis did not install and run firebox test. This may correct it.

* Change to firefox 47

Firefox 48 is not working with selenium, but Firefox 47.0.1 does work.  Hopefully this will work instead of 46.

See SeleniumHQ/selenium#2110

* Try firefox 47.0.1

Using firefox: latest or 47 travis Firefox tests don't run. Last try to see if 47.0.1 will work. Otherwise for now we should stick with `firefox: '46'.

* Change Firefox to use latest instead of 46

Per WCT issue  Polymer/web-component-tester#367 this should work.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.