# Try Tor Browser with WebTunnel Integration

**URL:** https://forum.torproject.org/t/try-tor-browser-with-webtunnel-integration/5761
**Category:** General Discussion
**Tags:** webtunnel, tor-browser
**Created:** [December 2, 2022, 1:59pm UTC](https://forum.torproject.org/t/try-tor-browser-with-webtunnel-integration/5761 "2022-12-02T13:59:35Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Shelikhoo](https://forum.torproject.org/letter_avatar_proxy/v4/letter/s/e36b37/32.png) [@Shelikhoo](https://forum.torproject.org/u/Shelikhoo)
#### Post date: [December 2, 2022, 1:59pm UTC](https://forum.torproject.org/t/try-tor-browser-with-webtunnel-integration/5761/1 "2022-12-02T13:59:35Z")

</div>

After months of planning and development Tor Browser with built in WebTunnel pluggable transport based on HTTPT.

## How to use it?

First, download specialized build of Tor Browser from [here](https://people.torproject.org/~shelikhoo/w000hxg0k71q/). Or alternatively build it from [source](https://gitlab.torproject.org/shelikhoo/tor-browser-build/-/tree/dev-webtunnelw).

You can enable WebTunnel with a custom bridge line. Here is one of it:

`Bridge webtunnel 192.0.2.3:1 url=https://n97jlbvjwy3iotetc0axrtu3mm7gq1gajqv7-80-78-24-44.sslip.io/939e42a2-8f3f-4645-9d7b-8b9be28b157e`

Like all non-stable version build of the tor browser, it is recommended to use it with caution, as it is not fully tested for the best security and stability.

## What is webtunnel’s advantage?

The communication with a webtunnel bridge is in HTTPS protocol, thus difficult to identify. Furthermore, the same network address can host a website in coexistence of the webtunnel bridge, making active probing less effective.

---

<div class="post-metadata">

### Author: ![Vort](https://forum.torproject.org/user_avatar/forum.torproject.org/vort/32/63_2.png) [@Vort](https://forum.torproject.org/u/Vort)
#### Post date: [December 3, 2022, 11:18am UTC](https://forum.torproject.org/t/try-tor-browser-with-webtunnel-integration/5761/2 "2022-12-03T11:18:59Z")

</div>

Does not work:

```nohighlight
Dec 03 11:56:35.000 [info] managed_proxy_stderr_callback(): Managed proxy at 'PluggableTransports\webtunnel-client.exe' reported via standard error: 2022/12/03 11:56:35 SOCKS accepted: {192.0.2.3:1 url=https://n97jlbvjwy3iotetc0axrtu3mm7gq1gajqv7-80-78-24-44.sslip.io/939e42a2-8f3f-4645-9d7b-8b9be28b157e map[url:[https://n97jlbvjwy3iotetc0axrtu3mm7gq1gajqv7-80-78-24-44.sslip.io/939e42a2-8f3f-4645-9d7b-8b9be28b157e]]}
Dec 03 11:56:35.000 [info] managed_proxy_stderr_callback(): Managed proxy at 'PluggableTransports\webtunnel-client.exe' reported via standard error: 2022/12/03 11:56:35 dial error: unrecognized reply
Dec 03 11:56:35.000 [info] managed_proxy_stderr_callback(): Managed proxy at 'PluggableTransports\webtunnel-client.exe' reported via standard error: 2022/12/03 11:56:35 Handler ended

```

---

<div class="post-metadata">

### Author: ![Shelikhoo](https://forum.torproject.org/letter_avatar_proxy/v4/letter/s/e36b37/32.png) [@Shelikhoo](https://forum.torproject.org/u/Shelikhoo)
#### Post date: [December 5, 2022, 11:45am UTC](https://forum.torproject.org/t/try-tor-browser-with-webtunnel-integration/5761/3 "2022-12-05T11:45:50Z")

</div>

It seems that the webtunnel process was crashed on server side. I have fixed it by restarting it. I will try to find out the root cause for the crash of the process.

---

<div class="post-metadata">

### Author: ![Vort](https://forum.torproject.org/user_avatar/forum.torproject.org/vort/32/63_2.png) [@Vort](https://forum.torproject.org/u/Vort)
#### Post date: [December 5, 2022, 12:12pm UTC](https://forum.torproject.org/t/try-tor-browser-with-webtunnel-integration/5761/4 "2022-12-05T12:12:24Z")

</div>

> [@Shelikhoo](#):
>
> I have fixed it by restarting it.

I confirm that it works now. Thanks.

---

<div class="post-metadata">

### Author: ![sparrow](https://forum.torproject.org/letter_avatar_proxy/v4/letter/s/9f8e36/32.png) [@sparrow](https://forum.torproject.org/u/sparrow)
#### Post date: [July 27, 2023, 6:07pm UTC](https://forum.torproject.org/t/try-tor-browser-with-webtunnel-integration/5761/5 "2023-07-27T18:07:48Z")

</div>

tested WEbTunnel with two bridges from [bridges.torproject.org](http://bridges.torproject.org) in tor alpha **win64-13.0a1**  
Didn’t notice any problem for connection during ~2 hours of web browsing. I think it’s 50% faster than obfs4 bridges . (my connection is very slow in general, about 730KB down and 60KB up, it’s hard for me to tell how much faster this type of bridges really are)

Country: **Iran**  
ISP: **Asiatech**  
log of first try with a bridge:

```auto
2023-07-27 11:56:55.437 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 11:56:55.440 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 11:56:55.450 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-07-27 11:56:55.450 [NOTICE] Switching to guard context "bridges" (was using "default")
2023-07-27 11:56:55.462 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-07-27 11:57:04.459 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 11:57:15.039 [NOTICE] Renaming old configuration file to "C:\Users\LOL\Desktop\tor alpha\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1"
2023-07-27 11:57:21.880 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-07-27 11:57:21.888 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-07-27 11:57:24.672 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2023-07-27 11:57:24.673 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2023-07-27 11:57:25.640 [WARN] Managed proxy "N/A" process terminated with status code 0
2023-07-27 11:57:25.640 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
2023-07-27 11:57:25.645 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
2023-07-27 11:57:28.798 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
2023-07-27 11:57:28.958 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
2023-07-27 11:57:29.836 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
2023-07-27 11:57:29.837 [NOTICE] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
2023-07-27 11:57:30.012 [NOTICE] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
2023-07-27 11:57:30.180 [NOTICE] Bridge 'WTBrlcaFUb5NJj' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2001:db8:77cb:5ce6:9995:7466:7ffa:b3f8]:443) based on the configured Bridge address.
2023-07-27 11:57:30.180 [NOTICE] new bridge descriptor 'WTBrlcaFUb5NJj' (fresh): $770EA6412C8D3997ABFFF7173A3E53F1D3660167~WTBrlcaFUb5NJj [G6J3fNC6WGVoBcoDh8Q7PgU6kBqWJXamxQvYs7YXFlE] at 95.216.211.192 and [2001:db8:77cb:5ce6:9995:7466:7ffa:b3f8]
2023-07-27 11:57:30.821 [NOTICE] Bootstrapped 30% (loading_status): Loading networkstatus consensus
2023-07-27 11:57:41.888 [NOTICE] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
2023-07-27 11:57:41.890 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 23/7180, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
2023-07-27 11:57:42.511 [NOTICE] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
2023-07-27 11:57:44.018 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 23/7180, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
2023-07-27 11:57:44.018 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 23/7180, and can only build 0% of likely paths. (We have 100% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
2023-07-27 11:58:55.875 [NOTICE] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
2023-07-27 11:58:55.877 [NOTICE] Bootstrapped 60% (loading_descriptors): Loading relay descriptors
2023-07-27 11:58:55.879 [NOTICE] Bootstrapped 66% (loading_descriptors): Loading relay descriptors
2023-07-27 11:58:57.234 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
2023-07-27 11:58:57.725 [NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
2023-07-27 11:58:57.727 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
2023-07-27 11:58:57.727 [WARN] Only one bridge (transport: 'webtunnel') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.
2023-07-27 11:58:59.877 [NOTICE] Bootstrapped 100% (done): Done

```

second try with another bridge added:

```auto
2023-07-27 12:06:59.124 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 12:06:59.124 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 12:06:59.263 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-07-27 12:06:59.269 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
2023-07-27 12:07:04.481 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2023-07-27 12:07:04.481 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
2023-07-27 12:07:04.889 [NOTICE] Bridge 'WTBrlcaFUb5NJj' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2001:db8:77cb:5ce6:9995:7466:7ffa:b3f8]:443) based on the configured Bridge address.
2023-07-27 12:07:04.890 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
2023-07-27 12:07:04.891 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
2023-07-27 12:07:05.476 [WARN] Managed proxy "N/A" process terminated with status code 0
2023-07-27 12:07:05.857 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
2023-07-27 12:07:07.469 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
2023-07-27 12:07:08.407 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
2023-07-27 12:07:08.408 [NOTICE] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
2023-07-27 12:07:08.578 [NOTICE] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
2023-07-27 12:07:08.990 [NOTICE] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
2023-07-27 12:07:09.196 [NOTICE] Bridge 'WTBrlcaFUb5NJj' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2001:db8:77cb:5ce6:9995:7466:7ffa:b3f8]:443) based on the configured Bridge address.
2023-07-27 12:07:18.705 [NOTICE] Bridge 'WTBrqb6XpehVfU' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2001:db8:4279:e683:5c82:c721:4453:18d]:443) based on the configured Bridge address.
2023-07-27 12:07:18.705 [NOTICE] new bridge descriptor 'WTBrqb6XpehVfU' (fresh): $09B01A4C251F17E28426E4FB60A317EFF93CC50B~WTBrqb6XpehVfU [QNX6gUK0fL4OWEMpeepyD5YXD8t69DMQxrHzrRC4rWg] at 216.238.69.151 and [2001:db8:4279:e683:5c82:c721:4453:18d]
2023-07-27 12:07:18.706 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
2023-07-27 12:07:19.026 [NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
2023-07-27 12:07:19.027 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
2023-07-27 12:07:21.120 [NOTICE] Bootstrapped 100% (done): Done
2023-07-27 12:07:25.064 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 12:08:44.545 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 13:06:08.416 [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
2023-07-27 13:06:53.297 [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
2023-07-27 13:07:43.430 [NOTICE] We tried for 15 seconds to connect to '[scrubbed]' using exit $5AA6370205AA611CED967BDB4D8EBCB9D5DB57A9~AllTheWorldsAStage [UusPHrbA7SADCLEEn7HM+nOeClu+wWa47I5RHbmkrZA] at 107.189.1.160. Retrying on a new circuit.
2023-07-27 14:03:41.566 [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
2023-07-27 14:05:33.761 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 14:11:53.164 [NOTICE] New control connection opened from 127.0.0.1.
2023-07-27 14:49:20.096 [NOTICE] New control connection opened from 127.0.0.1.

```
