webtunnel doesn’t support using a proxy. And I think is the same for obfs4. The only PT that does support passing a proxy is snowflake and it only supports SOCKS5 and not https proxy.
I have created an issue for this feature:
But I’m not sure when we’ll be able to fix it, merge requests are welcome
Can’t reply now to Cecylia Bocovich since in this moment can’t login in gitlab.torproject.org, but
There is support for http, socks5, and socks4a proxies already in lyrebird, and it definitely works with obfs4. It should work with webtunnel as well because the proxy is configured in lyrebird.go via the dialFn, which webtunnel then uses.
We might have to debug this user's configuration to see why it is failing for them.
NO! With WT, is does not proxies at all.
WITHOUT TOR PROXY
[notice] Tor 0.4.8.13 (git-e153e72c01315f86) running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.3, Liblzma N/A, Libzstd N/A and Glibc 2.39 as libc.
[notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
[notice] Read configuration file "/root/t/torrc_webtunnel".
[warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
[notice] Opening Socks listener on 0.0.0.0:9050
[notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
[warn] You are running Tor as root. You don't need to, and you probably shouldn't.
[notice] Bootstrapped 0% (starting): Starting
[notice] Starting with guard context "bridges"
[notice] Delaying directory fetches: No running bridges
[notice] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
[notice] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
[notice] Bootstrapped 10% (conn_done): Connected to a relay
[notice] Bootstrapped 14% (handshake): Handshaking with a relay
[notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
[notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
[notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
[notice] Bridge 'imgcdn4' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]:443) based on the configured Bridge address.
[notice] new bridge descriptor 'xxxxxxx' (fresh): $xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx~xxxxxx4 [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] at xxx.xx.xxx.xxx and [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
[notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
[warn] Only one bridge (transport: 'webtunnel') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.
[notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
[notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
[notice] Bootstrapped 100% (done): Done
WITH TOR PROXY (both HTTP and SOCKS5)
[notice] Tor 0.4.8.13 (git-e153e72c01315f86) running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.3, Liblzma N/A, Libzstd N/A and Glibc 2.39 as libc.
[notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
[notice] Read configuration file "/root/t/torrc_webtunnel".
[warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
[notice] Opening Socks listener on 0.0.0.0:9050
[notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
[warn] You are running Tor as root. You don't need to, and you probably shouldn't.
[notice] Bootstrapped 0% (starting): Starting
[notice] Starting with guard context "bridges"
[notice] Delaying directory fetches: No running bridges
[notice] Bridge 'imgcdn4' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]:443) based on the configured Bridge address.
[notice] new bridge descriptor 'xxxxxxx' (cached): $xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx4 [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] at xxx.xx.xxx.xxx and [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
[warn] Managed proxy failed to configure the pluggable transport's outgoing proxy. (proxy is not supported)
[warn] Managed proxy at 'pluggable_transports/webtunnel' failed the configuration protocol and will be destroyed.
[warn] Managed proxy "N/A" process terminated with status code 256
[warn] Can't use bridge at [scrubbed]: there is no configured transport called "webtunnel".
[warn] Only one bridge (transport: 'webtunnel') is configured. You should have at least two for conflux, for any transport that is not 'snowflake'.
[warn] We were supposed to connect to bridge '[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa]:443 ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RSA_ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' using pluggable transport 'webtunnel', but we can't find a pluggable transport proxy supporting 'webtunnel'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
[warn] We were supposed to connect to bridge '[xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]:443 ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RSA_ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' using pluggable transport 'webtunnel', but we can't find a pluggable transport proxy supporting 'webtunnel'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
[warn] Can't use bridge at [scrubbed]: there is no configured transport called "webtunnel".
[notice] Delaying directory fetches: No running bridges
[warn] Managed proxy failed to configure the pluggable transport's outgoing proxy. (proxy is not supported)
