Manage incoming connections from BrowserStack to your private servers

If you are using BrowserStack SDK, you can set the capabilities covered in this document within the browserstack.yml file:

Test localhost websites

Once you’ve enabled Local Testing connection, our remote browsers and mobile devices will be able to access localhost URLs.

Use your test scripts to access and interact with your localhost website (for example, localhost:3000). Set browserstackLocal capability to true in your browserstack.yml configuration file.

Force all requests to resolve through your internal network

You can force all traffic through your internal network even if the resources are publicly resolvable using Local Testing’s --force-local capability. This option resolves all requests (on our remote browsers and devices) through your local machine.

To enable this option, add the following capability to your browserstack.yml file:

After establishing the Local Testing connection, use your test scripts to access and interact with your internally-hosted website (for example, staging.example.com). Remember to set local capability to true in your test scripts.

Bypass invalid certificate warning while testing on local HTTPS websites

You can test local websites with SSL certificates on our remote browsers and devices through Local Testing. When you access local websites that have SSL certificates on the browsers, you might see an “invalid certificate” error:

Now, use your test scripts to access and interact with your local HTTPS websites (for example, https://localhost:3000 or https://staging.example.com). Remember to set local capability to true in your test scripts before you run them.

Test localhost websites

Once you’ve enabled Local Testing connection, our remote browsers and mobile devices will be able to access localhost URLs.

Use your test scripts to access and interact with your localhost website (for example, localhost:3000). Add the following snippet to your test scripts to set the local capability to true:

MutableCapabilities capabilities = new MutableCapabilities();
HashMap<String, Object> browserstackOptions = new HashMap<String, Object>();
browserstackOptions.put("local", "true");
capabilities.setCapability("bstack:options", browserstackOptions);

var capabilities = {
  'bstack:options' : {
    "local" : "true"
  }
}

ChromeOptions capabilities = new ChromeOptions();
Dictionary<string, object> browserstackOptions = new Dictionary<string, object>();
browserstackOptions.Add("local", "true");
capabilities.AddAdditionalOption("bstack:options", browserstackOptions);

$caps = array(
'bstack:options' => array(
    "local" => "true"
    )
)

bstack_options = {
    "local": "true"
}
options = ChromeOptions()
options.set_capability('bstack:options', bstack_options)

options = Selenium::WebDriver::Options.chrome
capabilities = {
  'bstack:options' => {
   "local" = "true"
  }
}

Force all requests to resolve through your internal network

You can force all traffic through your internal network even if the resources are publicly resolvable using Local Testing’s --force-local capability. This option resolves all requests (on our remote browsers and devices) through your local machine.

To enable this option, use one of the two ways to establish the Local Testing connection:

HashMap<String, String> bsLocalArgs = new HashMap<String, String>();
bsLocalArgs.put("forcelocal", "true");

var bs_local_args = { 'forceLocal': 'true' };

List<KeyValuePair<string, string>> bsLocalArgs = new List<KeyValuePair<string, string>>() {
  new KeyValuePair<string, string>("forcelocal", "true")
};

$bs_local_args = array("key" => "<browserstack-accesskey>", "forcelocal" => true);

bs_local_args = { "forcelocal": "true" }

bs_local_args = {"forcelocal" => "true"}

./BrowserStackLocal --key YOUR_ACCESS_KEY --force-local

BrowserStackLocal.exe --key YOUR_ACCESS_KEY --force-local

After establishing the Local Testing connection, use your test scripts to access and interact with your internally-hosted website (for example, staging.example.com). Remember to set local capability to true in your test scripts.

Bypass invalid certificate warning while testing on local HTTPS websites

You can test local websites with SSL certificates on our remote browsers and devices through Local Testing. When you access local websites that have SSL certificates on the browsers, you might see an “invalid certificate” error:

MutableCapabilities capabilities = new MutableCapabilities();
HashMap<String, Object> browserstackOptions = new HashMap<String, Object>();
browserstackOptions.put("acceptInsecureCerts", "true");
capabilities.setCapability("bstack:options", browserstackOptions);

var capabilities = {
 	'bstack:options' : {
 		"acceptInsecureCerts" : "true",
 	}
}

Dictionary<string, object> browserstackOptions = new Dictionary<string, object>();
browserstackOptions.Add("acceptInsecureCerts", "true");
capabilities.AddAdditionalOption("bstack:options", browserstackOptions);

$caps = array(
 	'bstack:options' => array(
 		"acceptInsecureCerts" => "true",
 	)
)

desired_cap = {
 	'bstack:options' : {
 		"acceptInsecureCerts": "true",
 	}
}

capabilities = {
 	'bstack:options' => {
 		"acceptInsecureCerts" => "true",
 	}
}

caps.setCapability("acceptSslCerts", "true");

var capabilities = {
  'acceptSslCerts' : 'true'
}

caps.SetCapability("acceptSslCerts", "true");

$caps['acceptSslCerts'] = "true";

caps['acceptSslCerts'] = True

caps['acceptSslCerts'] = 'true'

Now, use your test scripts to access and interact with your local HTTPS websites (for example, https://localhost:3000 or https://staging.example.com). Remember to set local capability to true in your test scripts before you run them.