Mac OSX error: Sauce Labs – Error fetching PAC

Posted on in Environment

I'm using Sencha Test together with the Sauce Labs browser farm. In order to see all the various browsers in my Sencha Test Studio, I have to setup a Sauce Labs Connect tunnel.

  1. You can download it from here:

  2. Extract the zip, and place the contents of the folder under this location:

  3. Create a new shell script, under /Users/username/bin/SauceLabs/ called “tunnel”:
    touch tunnel

  4. Open up this file:
    open tunnel

  5. Populate with the following contents, substituting the login name and access key with your own. You can find this in the Sauce Labs portal (

ulimit -n 8192
sauceconnect/bin/sc -u saucelabsusername -k mykey
  1. Save the script, then make it executable using this command:
    chmod +x tunnel

  2. Now run the script: ./tunnel

The result should be:

MacBook-Pro-3:Saucelabs leeboonstra$ ./tunnel
11 Mar 17:40:11 - Sauce Connect 4.3.13, build 1879 4494856
11 Mar 17:40:11 - Starting up; pid 19205
11 Mar 17:40:11 - Command line arguments: sauceconnect/bin/sc -u leeboonstra -k ****
11 Mar 17:40:11 - Using no proxy for connecting to Sauce Labs REST API.
11 Mar 17:40:11 - Resolving to took 16 ms.
11 Mar 17:40:12 - Started scproxy on port 59721.
11 Mar 17:40:12 - Please wait for 'you may start your tests' to start your tests.
11 Mar 17:40:12 - Starting secure remote tunnel VM...
11 Mar 17:40:17 - Secure remote tunnel VM provisioned.
11 Mar 17:40:17 - Tunnel ID: e506b17963574528b900eba652ec6958
11 Mar 17:40:18 - Secure remote tunnel VM is now: booting
11 Mar 17:40:20 - Secure remote tunnel VM is now: running
11 Mar 17:40:20 - Using no proxy for connecting to tunnel VM.
11 Mar 17:40:20 - Resolving tunnel hostname to took 44ms.
11 Mar 17:40:20 - Starting Selenium listener...
11 Mar 17:40:20 - Establishing secure TLS connection to tunnel...
11 Mar 17:40:20 - Selenium listener started on port 4445.
11 Mar 17:40:33 - Sauce Connect is up, you may start your tests.

However, in my case, I received an error:

11 Mar 17:30:54 - Sauce Connect 4.3.13, build 1879 4494856
11 Mar 17:30:54 - Detected PAC URL http://wpad/wpad.dat.
11 Mar 17:30:54 - Starting up; pid 18123
11 Mar 17:30:54 - Command line arguments: sauceconnect/bin/sc -u leeboonstra -k ****
11 Mar 17:30:54 - Error fetching PAC http://wpad/wpad.dat: Couldn't resolve host name.
11 Mar 17:30:54 - Sauce Connect could not establish a connection.
11 Mar 17:30:54 - Please check your firewall and proxy settings.
11 Mar 17:30:54 - You can also use sc --doctor to launch Sauce Connect in diagnostic mode.
11 Mar 17:30:54 - Goodbye.

This is how I solved it.
First I need to make sure outgoing port 443, is open:

nc -v 443

This seems to be ok.
The next thing that I need to check is my network proxy settings.

Open your network settings.
Click Advanced, Proxies tab. Make sure Auto Proxy Discovery is UNCHECKED.

Now try to run the tunnel again. ./tunnel
For me it worked!

How to get SOAP proxy to work in Sencha Architect?

Posted on in Architect Questions

The SOAP data proxy is part of the pro package in Ext JS, and isn't available in the GPL version (which is on the CDN). Therefore it also won't be visible in the Sencha Architect toolkit.

I don't have a SOAP server to test from, but I was able to make a test where the soap proxy & reader are at least loaded in the project. Here's what I did:

1) In project settings / framework, set it to "Commercial", i.s.o. custom paths.
That one, will use the local version of Ext JS 5.

2) In the requires for the application if have the following 2 files added:

3) Now, the most important step: Select "Resources" in the Project Inspector.
Click the + new button, in the top of the Project Inspector, and add 2 new JS resources.
You can point the urls to:
Once you've done that, the files are visible in the editors.

Once you have the soap proxy and reader fully loaded, you should be able to use it.

Although I am not an expert with the Soap proxy, I can point you out to one of our Soap guides.

In case you notice a bug in one of the 2 scripts, I would advise you to add ticket in the support portal. If it's indeed a framework bug, it won't cost you any support credits.