Skip to content

Webtunnel blocking in Russia - a report

Hi! This ticket is related to #40064. I used patched webtunnel-client referred to in here: #40064 (comment 3215660) My Arti config addition (lyrebird transport got commented out obviously):

[[bridges.transports]]
protocols = ["webtunnel"]
#proxy_addr = "127.0.0.1:31337"
path = "${PROGRAM_DIR}/pluggable-transports/webtunnel-client.exe"
arguments = ["-client chrome_131"]
run_on_startup = false

It worked for a few minutes, then stopped working. Then I added a few more webtunnels from a certain public source. Got this in my log and nothing was working:

2025-07-03T19:17:38Z  INFO arti::subcommands::proxy: Starting Arti 1.4.4 in SOCKS proxy mode on localhost port 9150 ...
2025-07-03T19:17:38Z  INFO arti_client::client: Running without a keystore
2025-07-03T19:17:39Z  INFO tor_ptmgr: Got a request for transport webtunnel, which is not currently running. Launching it.
2025-07-03T19:17:39Z  INFO tor_ptmgr: Got a request for transport webtunnel, which is not currently running. Launching it.
2025-07-03T19:17:39Z  INFO tor_ptmgr::ipc::sealed: Launching pluggable transport at C:\Users\Username\arti/pluggable-transports/webtunnel-client.exe for [PtTransportName("webtunnel")]
2025-07-03T19:17:40Z  INFO arti::reload_cfg: Successfully reloaded configuration.
2025/07/03 22:17:40 Started SOCKS listener at 127.0.0.1:4726.
2025-07-03T19:17:40Z  INFO tor_ptmgr::ipc::sealed: Transport 'webtunnel' uses method PtClientMethod { kind: V5, endpoint: 127.0.0.1:4726 }
2025-07-03T19:17:40Z  INFO tor_ptmgr::ipc: PT binary initialisation done
2025-07-03T19:17:40Z  INFO tor_ptmgr: Successfully launched PT for webtunnel at PtClientMethod { kind: V5, endpoint: 127.0.0.1:4726 }.
2025-07-03T19:17:40Z  INFO tor_ptmgr: Successfully launched PT for webtunnel at PtClientMethod { kind: V5, endpoint: 127.0.0.1:4726 }.
2025/07/03 22:17:40 SOCKS accepted: {[2001:db8:aa16:aa07:b3:b4f0:a667:3f08]:443 url=https://pod01.oneclickhost.eu/<auth>;ver=0.0.2,;servername=yandex.ru  map[servername:[yandex.ru] url:[https://pod01.oneclickhost.eu/<auth>] ver:[0.0.2,]]}
2025/07/03 22:17:40 SOCKS accepted: {[2001:db8:e73c:13d:2f1d:1d27:5531:a599]:443 url=https://nl.808.re/<auth>;ver=0.0.2,;servername=yandex.ru  map[servername:[yandex.ru] url:[https://nl.808.re/<auth>] ver:[0.0.2,]]}
2025/07/03 22:17:40 Lookup error for host pod01.oneclickhost.eu: lookup pod01.oneclickhost.eu: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2025/07/03 22:17:40 Handler ended
2025/07/03 22:17:40 SOCKS accepted: {[2001:db8:aa16:aa07:b3:b4f0:a667:3f08]:443 url=https://pod01.oneclickhost.eu/<auth>;ver=0.0.2,;servername=yandex.ru  map[servername:[yandex.ru] url:[https://pod01.oneclickhost.eu/<auth>] ver:[0.0.2,]]}
2025/07/03 22:17:40 Lookup error for host pod01.oneclickhost.eu: lookup pod01.oneclickhost.eu: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2025/07/03 22:17:40 Handler ended
2025/07/03 22:17:41 SOCKS accepted: {[2001:db8:aa16:aa07:b3:b4f0:a667:3f08]:443 url=https://pod01.oneclickhost.eu/<auth>;ver=0.0.2,;servername=yandex.ru  map[servername:[yandex.ru] url:[https://pod01.oneclickhost.eu/<auth>] ver:[0.0.2,]]}
2025/07/03 22:17:41 Lookup error for host pod01.oneclickhost.eu: lookup pod01.oneclickhost.eu: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
2025/07/03 22:17:41 Handler ended
2025/07/03 22:17:41 SOCKS accepted: {[2001:db8:aa16:aa07:b3:b4f0:a667:3f08]:443 url=https://pod01.oneclickhost.eu/<auth>;ver=0.0.2,;servername=yandex.ru  map[servername:[yandex.ru] url:[https://pod01.oneclickhost.eu/<auth>] ver:[0.0.2,]]}
2025/07/03 22:17:41 Lookup error for host pod01.oneclickhost.eu: lookup pod01.oneclickhost.eu: getaddrinfow: This is usually a temporary err

My ISP is MegaFon. Pretty sure they have the latest DPI hw, none of my old ways are working on it.

DPI here is getting Chinese tier, the good days are over.

I may not be there to reply to this issue, this is just to inform how things work on our end.

Edited by David Fifield