Release history
Every released version of TestingBot Tunnel, newest first. New features, improvements and bug fixes.
-
v5.2
November 2026, latest release- HTTPS from iOS devices, iOS simulators and macOS Safari works again through the tunnel. iOS and macOS send a
CONNECTwhoseHostheader has no port, and since 5.0 the tunnel answered it with 400 instead of connecting; only clients that include the port (Android, Chrome, curl) got through - TestCafe works again through the tunnel: the page URL that TestCafe embeds in its proxy path is relayed unchanged instead of answered with 400 "Ambiguous URI empty segment", which ended runs in "browser disconnected"
- Only the client's
User-Agentis forwarded on plain HTTP. Jetty's was sent as a second one, which made TestCafe report the browser as "Other 0.0"
- HTTPS from iOS devices, iOS simulators and macOS Safari works again through the tunnel. iOS and macOS send a
-
v5.1
October 2026- Several SSH connections to the tunnel server:
--ssh-connections N(1-8, default 4). One slow or dropped connection no longer holds up the others, and each reconnects on its own. On a tunnel server that cannot spread traffic over them, the tunnel uses one connection, as before - Uploads through the tunnel are up to 10x faster at real-world latency: each forwarded connection's window is 2 MB instead of 128 KB, which capped every connection at 128 KB per round trip
- A dead connection is noticed in about 6 seconds instead of up to 15 minutes after a network change (VPN reconnect, Wi-Fi switch), and the tunnel reconnects straight away
- Browser traffic keeps flowing through reconnects: the tunnel re-requests and checks its connection to the tunnel server, and repairs it if it stopped delivering
- PAC files (
--pac-local): a failover list such asPROXY a; DIRECTfalls through to the next entry when a proxy cannot be reached,isInNet()resolves host names, and an invalid PAC file is reported before a tunnel server is started -
--noproxywithout--localproxyuses port 8087, as its help text says - An incomplete response from the TestingBot API is reported plainly instead of as a stack trace
- Startup no longer logs two failed warm-up requests
- The Windows self-contained build is available again
- Several SSH connections to the tunnel server:
-
v5.0
October 2026- Breaking: requires Java 17 (was 11). On an older Java the tunnel now says so plainly. Or use a new self-contained build that needs no Java
-
Breaking: local listeners (Selenium relay, local proxy, metrics port,
--web) bind127.0.0.1instead of every interface. Use--bind-address 0.0.0.0to accept connections from other machines. The Docker image sets this for you -
Breaking: successful requests no longer log a line.
--log-httpdefaults toerrors;--log-http urlrestores the 4.x behaviour. See upgrading from 4.x - New self-contained downloads for Linux x64/arm64, macOS Intel/Apple silicon (signed and notarized) and Windows x64, with a
.sha256for every file - Built on Jetty 12
- Restrict what the tunnel can reach:
--allow-hosts,!exceptions in--fast-fail-regexpsand--localhost-policy deny, enforced on HTTP, CONNECT and WebSocket upgrades. See traffic rules - Corporate networks:
--pac-localto choose egress per destination from a PAC file, Kerberos/SPNEGO with--proxy-auth-scheme negotiateand--krb5-hosts, a separate--proxy-testingbot,--cacert-filefor TLS-intercepting proxies, SOCKS5 upstream proxies,--connect-to,--ws-proxy-mode, multi-server--dnsand--http-dial-timeout/--http-idle-timeout - Security: pin the tunnel server's SSH host key with
--ssh-host-keyand--ssh-host-key-policy require; upstream proxy credentials are only sent to the proxy they belong to; credentials are redacted from logs - Operations:
/healthzand/readyzendpoints,--readyfor health checks, and aHEALTHCHECKin the Docker image./readyznow reports ready only after the startup self-test passes - Logging:
--log-httpper module (proxy:,forwarder:),--log-format jsonand request-id correlation - Configuration:
--configfile and aTESTINGBOT_*environment variable for nearly every option -
--headerand--response-headerto add, replace or remove headers on plain HTTP - Failed requests now say why, with an
X-TestingBot-Errorheader and a readable message - More resilient reconnects, and
--doctordiagnoses the configuration it is actually given - The tunnel can be embedded as a Java library with
boot(),awaitReady()andstop(). See embedding
-
v4.9
August 2026- Fixed reverse port forwarding on macOS: every request through the tunnel failed with a
502 Bad Gatewaywhile the tunnel reported itself healthy - The tunnel now verifies at startup and continuously that reverse forwarding can deliver traffic, and reports failures prominently instead of silently ignoring them
- A failed startup self-test no longer prints "The Tunnel is ready"
-
--log-level debugno longer writes credentials to the log - Fixed HTTPS CONNECT host handling for
--fast-fail-regexpsmatching and logging - Updated dependencies (security fixes)
- Fixed reverse port forwarding on macOS: every request through the tunnel failed with a
-
v4.8
May 2026- Added a Prometheus
/metricsendpoint exposing HTTP request rate, duration and size histograms, HTTPS CONNECT counters, SSH tunnel state and reconnects, active connections, error counters and JVM/process metrics - Added
--metrics-auth user:passwordto protect the metrics endpoint with HTTP Basic Authentication - Added
TESTINGBOT_AUTH,TESTINGBOT_PROXY_USERPWDandTESTINGBOT_METRICS_AUTHenvironment variables so credentials stay out of the process list - Sensitive headers are now stripped from debug logging
- Improved basic authentication handling and logging
- Updated dependencies
- Added a Prometheus
-
v4.7
March 2026- Fixed an issue with WebSocket proxying
-
v4.6
January 2026- Fixed an issue with
--debug
- Fixed an issue with
-
v4.5
January 2026- Added
-s,--sharedto share a tunnel with colleagues on your team. Tunnels are not shared by default - Updated dependencies
- Code improvements
- Added
-
v4.4
October 2025- Improved
--proxyand--proxy-userpwdreliability - Updated dependencies
- Improved
-
v4.3
August 2025- Enhanced
--doctordiagnostic checks - Improved connection monitoring and automatic retry mechanisms
- Updated Jetty and SSH libraries
- Dropped support for Java 8 (Java 11+ now required)
- Enhanced
-
v4.0
December 2024- Added WebSocket and Server-Sent Events (SSE) support
- Added
--nobumpoption to disable SSL bumping - Upgraded to Jetty 11
-
v3.5
May 2023- Upgraded secure connection ciphers for improved security
- Updated dependencies
-
v3.2
February 2021- Updated dependencies for security and compatibility
-
v3.1
February 2020- Fixed tunnel polling to prevent indefinite connection attempts
- Built with Java 8 for broader compatibility
- Internal code improvements
-
v3.0
September 2019- Updated Jetty dependencies
- Various stability improvements
-
v2.9
January 2019- Various minor fixes to timeout handling and
--doctorchecks
- Various minor fixes to timeout handling and
-
v2.8
June 2018- Fixed null pointer exception in connection handler
-
v2.7
June 2018- Added upstream HTTPS proxy support via CONNECT method (
--proxy) - Renamed
--jettyportoption to--localport - Enabled
--nocacheintegration with Manual Testing API - Removed hardcoded port restrictions
- Added upstream HTTPS proxy support via CONNECT method (
-
v2.6
April 2018- Added option to inject custom HTTP headers into requests
- Added automatic basic authentication for configured hosts
- Clarified
--nocachebehavior: disables all HTTP request caching - Removed deprecated
--boostand--ssloptions - Fixed incorrect Java version detection
-
v2.5
September 2017- The tunnel now reports its version to TestingBot
- Added
--pacoption to configure a PAC (Proxy Auto-Config) URL for test sessions
-
v2.4
August 2017- Added
--tunnel-identifierto run multiple tunnels on the same account - Added local directory serving for static file testing
- Added embedded REST API for tunnel statistics (default port 8003)
- Improved logging with configurable output format, file logging, and debug levels
- Improved connection error handling with automatic reconnection
- Added
-
v2.3
October 2016- Added
--doctorcommand to troubleshoot configuration issues - Debug mode now outputs HTTP headers for easier troubleshooting
- Added