diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index 911329a10..69f218ddf 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE.md @@ -1,3 +1,5 @@ +# Submit Issue + Verify first that your issue/request has not been posted previously: * https://github.com/beefproject/beef/issues @@ -5,45 +7,60 @@ Verify first that your issue/request has not been posted previously: Ensure you're using the [latest version of BeEF](https://github.com/beefproject/beef/releases/tag/beef-0.5.0.0). +Please do your best to provide as much information as possible. It will help substantially if you can enable and provide debugging logs with your issue. Instructions for enabling debugging logs are below: -#### Environment +1. In the `config.yaml` file of your BeEF root folder set debug and client_debug (lines 11 & 13 respectively) to `true` + * If using a standard installation of `beef-xss` the root folder will typicaly be `/usr/share/beef-xss` +2. Reproduce your error +3. Retrieve your client-side logs from your browser's developer console (Ctrl + Shift + I) +4. Retrieve your server-side logs from `~/.beef/beef.log` +5. **If using `beef-xss`:** Retrieve your service logs using `journalctl -u beef-xss` -What version/revision of BeEF are you using? +Thank you, this will greatly aid us in identifying the root cause of your issue :) -On what version of Ruby? +**If we request additional information and we don't hear back from you within a week, we will be closing the ticket off.** +Feel free to open it back up if you continue to have issues. -On what browser? +## Summary -On what operating system? +**Q:** Please provide a brief summary of the issue that you experienced. +**A:** + +## Environment + +*Please identify the environment in which your issue occurred.* + +1. **BeEF Version:** + +2. **Ruby Version:** + +3. **Browser Details (e.g. Chrome v81.0):** + +4. **Operating System (e.g. OSX Catalina):** -#### Configuration +## Configuration -Are you using a non-default configuration? +**Q:** Have you made any changes to your BeEF configuration? +**A:** -Have you enabled or disabled any BeEF extensions? +**Q:** Have you enabled or disabled any BeEF extensions? +**A:** + +## Expected vs. Actual Behaviour + +**Expected Behaviour:** +
+**Actual Behaviour:** +
+ +## Steps to Reproduce + +*Please provide steps to reproduce this issue.* + +1. -#### Summary +## Additional Information -Please provide a summary of the issue. - - -#### Expected Behaviour - -What was the expected result? - - -#### Actual Behaviour - -What was the actual result? - - -#### Steps to Reproduce - -Please provide steps to reproduce this issue. - - -#### Additional Information - -Please provide any additional information which may be useful in resolving this issue, such as debugging output and relevant screen shots. Debug output can be enabled by specifying `debug: true` in the `config.yaml` configuration file. +Please provide any additional information which may be useful in resolving this issue, such as debugging output and relevant screen shots. Debug output can be retrieved by following the instructions towards the top of the issue template. diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 27bc46604..fe9f18916 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,26 +1,20 @@ +# Pull Request + Thanks for submitting a PR! Please fill in this template where appropriate: ## Category - -(Bug / module / extension / core functionality / documentation / tests) +*e.g. Bug, Module, Extension, Core Functionality, Documentation, Tests* ## Feature/Issue Description +**Q:** Please give a brief summary of your feature/fix +**A:** -This Module is added to ... -This Extension is used by doing ... -This Bug can be reproduced by ... -The Documentation describes ... -This Test covers ... +**Q:** Give a technical rundown of what you have changed (if applicable) +**A:** +## Test Cases +**Q:** Describe your test cases, what you have covered and if there are any use cases that still need addressing. +**A:** -## Describe what changes -Describe how the change affects BeEF's usability ... -Describe how to replicate the issue/bug that this is fixing ... -Describe what this improves - -## Test cases -Describe what the goal of the test is, what it covers and if there are any use cases that still need to be covered. -spec/beef/extensions/example_extension.rb - -## Relevant wiki page -If it is not easily understandable without little pre-knowledge or context, there should be a section in the Wiki somewhere explaining it. +## Wiki Page +*If you are adding a new feature that is not easily understood without context, please draft a section to be added to the Wiki below.* diff --git a/local.log b/local.log deleted file mode 100644 index e8736d9ac..000000000 --- a/local.log +++ /dev/null @@ -1,2117 +0,0 @@ - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - -Press Ctrl-C to exit - - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing - - -BrowserStackLocal v7.6 - -You can now access your local server(s) in our remote browser. - - -BrowserStackLocal v7.6 - - *** Error: Either another browserstack local client is running on your machine or some server is listening on port 45691 - -To test an internal server, run: -./BrowserStackLocal --key -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 - -To test HTML files, run: -./BrowserStackLocal --key --folder -Example: -./BrowserStackLocal --key DsVSdoJPBi2z44sbGFx1 --folder /Applications/MAMP/htdocs/example/ - - -The following options are available: - -k, --key Browserstack Access Key. This information is available in the local testing section of the Settings page: https://www.browserstack.com/accounts/settings - -f, --folder Specify the Local folder to be used for testing. This option is to be used when testing a local folder. Example: /home/ubuntu/mysite/ or C:\windows\mysite\ - -h, --help Display the help text. - -V, --version Display the current version of the binary. - -F, --force Using this option kills all other instances of BrowserStack Local binary running on this machine with the same --local-identifier options. This option will not affect binaries running in remote servers and instances running with different --local-identifier options. - --only If you want to restrict BrowserStackLocal Binary access to few local servers and/or folders, use this option to restrict them. Usage: host1,port1,ssl?,host2,port2,ssl?. Example: localhost,8000,0,abc.example.com,8080,1 - --force-local Route all traffic via machine where BrowserStackLocal Binary is running. Local tries to fetch public urls directly, unless this option is specified. - --verbose This option sets the level of logging required. Set 1 to debug issues related to setting up connections. Set 2 for logs related to network information. Set 3 to dump all communication to local servers for each request and response. The default value for this option is 1. - --only-automate This option restricts Binary usage to Automate product, and it cannot be used for Live/Screenshot testing. - --proxy-host If you are behind corporate proxy setup, please specify your proxy host using this option. - --proxy-port If you are behind corporate proxy setup, please specify your proxy port using this option. Default value is 3128. - --proxy-user If you are behind corporate proxy which requires authentication, please specify your proxy username using this option. As of now, only HTTP Basic authentication is supported. - --proxy-pass If you are behind corporate proxy which requires authentication, please specify your proxy password using this option. As of now, only HTTP Basic authentication is supported. - --local-identifier If you are running multiple copies of BrowserStackLocal binary (for better performance or other reasons), please specify unique strings for BrowserStack to uniquely identify them. You will need to specify the same string in Automate tests as well. - --force-proxy This options routes all traffic via the proxy specified - otherwise, binary tries to connect directly as well for better performance. - --local-proxy-host If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy host using this option. - --local-proxy-port If your local server is behind a proxy or you are using a proxy to log all communication to your local servers - please specify your proxy port using this option. Default assumed is 8081. - --local-proxy-user If your local server is behind a proxy, and it requies authentication - please specify your proxy username using this option. - --local-proxy-pass If your local server is behind a proxy, and it requies authentication - please specify your proxy password using this option. - --daemon Starts or stop the binary as a daemon. Accepts only 2 commands: start, stop. Start will start binary in background. Primarily used in Continous Integration server scripts. - --enable-logging-for-api Include this option to make sure this binary is exposed to Local API for debugging. For more information refer to https://www.browserstack.com/local-testing#local-api-debugging - --log-file Logs all the output to the file specified. - --pac-file Path to pac file with which the proxy needs to be set. - --parallel-runs Specify the number of parallel runs. - --disable-proxy-discovery Disables the Auto-Proxy Discovery - --debug-utility Start BrowserStackLocal in debug mode. - --debug-url Internal/Staging URL BrowserStackLocal will try to connect when started in debug mode. - --https-ports If you want to test local HTTPS server which behind a proxy, in addition to port 443, please pass comma separated port values. Example: --https-ports 8443,9443 - -View more configuration options at https://www.browserstack.com/local-testing -