Skip to content
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.

Cannot run the service behind corporate proxy #34

Open
kukuruznik opened this issue Dec 6, 2017 · 2 comments
Open

Cannot run the service behind corporate proxy #34

kukuruznik opened this issue Dec 6, 2017 · 2 comments

Comments

@kukuruznik
Copy link

Our proxy rules ban AWS. As the service is starting it does an attempt to download the latest selenium drivers and fails. The startup fails even when there are already some downloaded binaries from previous runs (downloaded via direct Internet access).

Proposed solution:
Make the download optional - e.g. don't reject the promise when the download fails and let Selenium run with an older driver (if exists).

If you accept such a solution I am willing to create a pull request with the change.

@joshden
Copy link

joshden commented Mar 8, 2018

Might be good to have some kind of option to ignore failures or not even attempt downloading the latest drivers. If we make this the default behavior to not fail on such failures, it might lead to a download failure being unintentionally not noticed.

@inspiraller
Copy link

I had the same problem. I developed a workaround by downloading the selenium server java file and chromedriver manually, using gulp plus node run cmd package to run dual cmds, updating some arguments in capabalities, and removing the reference in wdio.conf which refers to services. Here is my solution: https://github.com/inspiraller/cucumber-boilerplate-behind-corporate-network

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants