error trying to use this browser provider with travis
4kategreen opened this issue · comments
i'm having trouble setting up this browser provider for use with travis. we used the instructions from the docs, though we're using make to kick off the tests instead of from the package.json test link.
i am able to use the same command with the same creds locally and i can set up a sauce connect tunnel using travis's sauce connect addon with the same creds. here are the logs from the travis attempt:
2018-10-31 21:09:23.690 [5055] Sauce Connect 4.5.1, build 4191 13eede5 -dirty
2018-10-31 21:09:23.690 [5055] Using CA certificate bundle /etc/ssl/certs/ca-certificates.crt.
2018-10-31 21:09:23.690 [5055] Using CA certificate verify path /etc/ssl/certs.
2018-10-31 21:09:23.690 [5055] Trying to autodetect proxy settings
2018-10-31 21:09:23.691 [5055] Starting up; pid 5055
2018-10-31 21:09:23.691 [5055] Command line arguments: /home/travis/build/LuminalHQ/risk-manager/tests/e2e/node_modules/sauce-connect-launcher/sc/sc-4.5.1-linux/bin/sc -u luminal_web -k **** --tunnel-identifier 1541020160197 --direct-domains *.google.com,*.gstatic.com,*.googleapis.com --logfile sc_1541020160197.log --readyfile /tmp/sc-launcher-readyfile
2018-10-31 21:09:23.692 [5055] Log file: sc_1541020160197.log
2018-10-31 21:09:23.692 [5055] Pid file: /tmp/sc_client-1541020160197.pid
2018-10-31 21:09:23.692 [5055] Timezone: UTC GMT offset: 0h
2018-10-31 21:09:23.692 [5055] Using no proxy for connecting to Sauce Labs REST API.
2018-10-31 21:09:24.257 [5055] PROXY *** scproxy started ***
2018-10-31 21:09:24.258 [5055] PROXY found DNS server 169.254.169.254
2018-10-31 21:09:24.307 [5055] Started scproxy on port 44414.
2018-10-31 21:09:24.307 [5055] Please wait for 'you may start your tests' to start your tests.
2018-10-31 21:09:24.642 [5055] error querying from https://saucelabs.com/rest/v1/luminal_web/tunnels?full=1, error was: {"message": "Not authorized"}. HTTP status: 401 Unauthorized
2018-10-31 21:09:24.642 [5055] Sauce Connect could not establish a connection.
2018-10-31 21:09:24.642 [5055] Please check your firewall and proxy settings.
2018-10-31 21:09:24.642 [5055] You can also use the sc --doctor to launch Sauce Connect in diagnostic mode.
2018-10-31 21:09:24.642 [5055] Goodbye.
the command we're using to kick off the build: testcafe "saucelabs:Firefox@62.0:Windows 10" --selector-timeout 30000 --assertion-timeout 30000 --page-load-timeout 30000 suites/**/*.js, which works as expected locally.
nm. close this. we debugged it and found the problem on our side.
Thank you for the update. I'm happy to hear that you have figured out how to resolve the issue.