Advanced configuration of device tunneling

Fine-tune your setup to resolve port conflicts, manage concurrent sessions, or integrate with automated CI/CD workflows.

By creating a device-tunnel.yml configuration file, you can customize key settings for server ports, iOS connections, and logging verbosity to better suit your environment. This guide provides advanced configuration options for setting up device tunneling, enabling seamless local testing and debugging.

Configuration file example

Place the following device-tunnel.yml file in the same directory as your browserstack-sdk binary.

Parameter details

• orchestrator_port: The local port the orchestrator process listens on.

• base_port: The starting local port that remote devices will be mapped to. For example, the first device will connect to localhost:7005, the second to localhost:7006, and so on. This option is available only for Android devices.

• max_concurrent_tunnels: The maximum number of tunnels that can be active at one time.

• enable_ios: Must be set to true to enable tunneling for iOS devices.

• system_authentication (macOS only): Your user password, required for the tool to manage the usbmuxd socket for iOS testing in automated environments.

• log_level: Controls the verbosity of logs. Useful for debugging. Can be set to error, warn, info, or debug.

Related topics

• Device tunneling overview - Understand the benefits and prerequisites of device tunneling.
• Getting started - Install the tool and run your first tunnel.
• iOS setup guide - Configure your macOS environment for iOS device tunneling.
• CLI reference & management - Explore command-line options for managing device tunnels
• Troubleshooting guide - Find solutions to common issues with device tunneling.