-
Bug
-
Resolution: Done
-
Major
-
Linux, Jenkins ver. 1.523, Sauce OnDemand Plugin v. 1.67
I am trying to start Sauce Connect tunnel that uses my proxy server for connections by means of Sauce OnDemand Plugin. To do that I entered "-p localhost:5000" (without quotes) to the Sauce Connect Options field within Sauce Connect Advanced Options section of my Jenkins job config. When Jenkins job starts, log message appears that Sauce Connect was successfully started, though, when my java code (that is run by Jenkins job) tries to start the remote WebDriver (normal URL:http://<account>:<apikey>@localhost:4445/wd/hub), it fails with "UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure." exception.
It looks like tunnel did not start at all when "--proxy" argument was provided in options (once I removed this argument, tunnel was successfully started without proxy usage).
[JENKINS-21874] Can't start Sauce Connect with proxy
Ross Rowe
added a comment - Hi, sorry it's taken so long to respond to your issue, would you be able to tell me if the error still occurs using the latest version of the plugin (version 1.83)? Please note that the latest version uses Sauce Connect v4 by default, which has slightly different command line args.
Cheers,
Ross
Ross Rowe
added a comment - Hi, sorry it's taken so long to respond to your issue, would you be able to tell me if the error still occurs using the latest version of the plugin (version 1.83)? Please note that the latest version uses Sauce Connect v4 by default, which has slightly different command line args.
Cheers,
Ross Hi, @Ross
I was using old version of the plugin (1.67).
I just upgraded to the latest (1.83) but, I'm not able to check if the issue still persists as we found another solution to run Sauce Connect.
We run it directly from our code (see SauceConnectManager.java attached, let me know if you need further details).
Though, it produces huge output to console/file so we suspect it affects performance, so we are thinking of trying a new version of Sauce OnDemand plugin later.
P.S. All above is about Sauce Connect v.3 (yes, we still use it!), but moving to v.4 is scheduled so we expect lover verbosity in it as well.
Andrei Khveras
added a comment - - edited Hi, @Ross
I was using old version of the plugin (1.67).
I just upgraded to the latest (1.83) but, I'm not able to check if the issue still persists as we found another solution to run Sauce Connect.
We run it directly from our code (see SauceConnectManager.java attached, let me know if you need further details).
Though, it produces huge output to console/file so we suspect it affects performance, so we are thinking of trying a new version of Sauce OnDemand plugin later.
P.S. All above is about Sauce Connect v.3 (yes, we still use it!), but moving to v.4 is scheduled so we expect lover verbosity in it as well. Hi tenety,
Sauce Connect three is far out of date and no longer support, my best advise is to concentrate efforts on upgrading to the latest version of the plugin or Sauce Connect as there are a large number of security and bug enhancements that Sauce Connect three is missing. With that in mind, I am going to close this case but should you encounter this issue with the latest version of the plugin please feel free to open a new case.
Cheers,
Andrew
Please, let me know if you need any further details