[Bug]: middle-proxy handshake failed

[d0bro]

Proxy version

v0.19.0

OS & kernel

Linux 6.12.74+deb13+1-amd64

Telegram client & version

Telegram Desktop 6.7.6/ Forkgram Android 12.6.5.0 (66660)

Pre-flight checklist

• I am running the latest release (checked Releases).
• System clock is synchronized (timedatectl status shows NTP synchronized: yes).
• The proxy port (default 443) is open in the firewall (ss -tlnp | grep <port> shows LISTEN).
• I can reach the proxy port from the outside (curl -v --connect-timeout 5 https://<server-ip>:<port> returns a TLS error, not a timeout).
• Secret key in config.toml matches the tg:// link I use on the client (I re-checked byte-for-byte).
• RLIMIT_NOFILE warning (if present) is just a warning — I understand it does not block connections.
• I have read the logs with journalctl -u mtproto-proxy -n 200 --no-pager and the full output is attached below.

config.toml (secrets redacted)

[general]
use_middle_proxy = true

[server]
port = 443
bind_address = 0.0.0.0
max_connections = 2000
middleproxy_buffer_kb = 1024
tag = "tut tag"
unsafe_override_limits = true

[censorship]
tls_domain = "my domain"
mask = true
mask_port = 4433
fast_mode = true

[access.users]
d0b = "secret"

[upstream]
type = "tunnel"

[upstream.tunnel]
interface = "wg0"

Full proxy log (last 200 lines)

Apr 18 02:12:37 renesmee mtproto-proxy[2432554]:   ──────────────────────────────────────────────────
Apr 18 02:12:37 renesmee mtproto-proxy[2432554]:   ⏳ Waiting for connections...
Apr 18 02:12:37 renesmee mtproto-proxy[2432554]: info(proxy): mask_port=4433 configured, using local mask target 127.0.0.1
Apr 18 02:12:37 renesmee mtproto-proxy[2432554]: info(proxy): Mask target '127.0.0.1:4433' resolved at startup
Apr 18 02:12:37 renesmee mtproto-proxy[2432554]: info(proxy): Using server.public_ip for middle-proxy NAT translation: 111.111.111.92 (тут ip от сервера в РФ) 
Apr 18 02:12:37 renesmee mtproto-proxy[2432554]: info(proxy): Upstream mode: direct (auto)
Apr 18 02:12:37 renesmee mtproto-proxy[2432554]: info(proxy): Listening on 0.0.0.0:443 (epoll, single-thread)
Apr 18 02:12:38 renesmee mtproto-proxy[2432554]: info(proxy): Middle-proxy cache updated: dc4=.{ .any = .{ .family = 2, .data = { 34, 184, 91, 108, 4, 147, 0, 0, 0, 0, 0, 0, 0, 0 } }, .in = .{ .sa = .{ .family = 2, .port = 47138, .addr = 2466540635, .zero = { ... } } }, .in6 = .{ .sa = .{ .family = 2, .port = 47138, .flowinfo = 2466540635, .addr = { ... }, .scope_id = 0 } }, .un = .{ .family = 2, .path = { 34, 184, 91, 108, 4, 147, 0, 0, 0, 0, 0, 0, 0, 0, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 64, 0, 0, 0, 0, 0, 0, 0, 224, 140, 206, 77, 254, 127, 0, 0, 56, 198, 239, 114, 194, 127, 0, 0, 192, 196, 239, 114, 194, 127, 0, 0, 208, 194, 0, 1, 0, 0, 0, 0, 120, 118, 206, 77, 254, 127, 0, 0, 0, 16, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } } } dc203=.{ .any = .{ .family = 2, .data = { 1, 187, 91, 105, 192, 110, 0, 0, 0, 0, 0, 0, 0, 0 } }, .in = .{ .sa = .{ .family = 2, .port = 47873, .addr = 1858103643, .zero = { ... } } }, .in6 = .{ .sa = .{ .family = 2, .port = 47873, .flowinfo = 1858103643, .addr = { ... }, .scope_id = 0 } }, .un = .{ .family = 2, .path = { 1, 187, 91, 105, 192, 110, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } } } secret_len=128
Apr 18 02:12:38 renesmee mtproto-proxy[2432554]: warning(proxy): [0] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:12:38 renesmee mtproto-proxy[2432554]: warning(proxy): [1] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:12:38 renesmee mtproto-proxy[2432554]: warning(proxy): [3] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:12:38 renesmee mtproto-proxy[2432554]: warning(proxy): [2] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:12:48 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=4/2000 hs_inflight=0 accepted+=4 closed+=0 tracked_fds=8 total=4 paused=false/false
Apr 18 02:12:48 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=0 hs_budget+=0 hs_timeout+=0 mp_fallback+=4
Apr 18 02:12:58 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=4/2000 hs_inflight=0 accepted+=1 closed+=1 tracked_fds=8 total=5 paused=false/false
Apr 18 02:13:08 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=4/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=8 total=5 paused=false/false
Apr 18 02:13:09 renesmee mtproto-proxy[2432554]: warning(proxy): [5] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:13:18 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=1 closed+=0 tracked_fds=10 total=6 paused=false/false
Apr 18 02:13:18 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=0 hs_budget+=0 hs_timeout+=0 mp_fallback+=1
Apr 18 02:13:28 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=6 paused=false/false
Apr 18 02:13:38 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=6 paused=false/false
Apr 18 02:13:48 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=6 paused=false/false
Apr 18 02:13:53 renesmee mtproto-proxy[2432554]: warning(proxy): [6] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:13:53 renesmee mtproto-proxy[2432554]: warning(proxy): [7] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:13:54 renesmee mtproto-proxy[2432554]: warning(proxy): [8] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:13:55 renesmee mtproto-proxy[2432554]: warning(proxy): [9] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:13:58 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=8/2000 hs_inflight=0 accepted+=4 closed+=1 tracked_fds=16 total=10 paused=false/false
Apr 18 02:13:58 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=0 hs_budget+=0 hs_timeout+=0 mp_fallback+=4
Apr 18 02:14:08 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=8/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=16 total=10 paused=false/false
Apr 18 02:14:11 renesmee mtproto-proxy[2432554]: warning(proxy): [10] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:14:18 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=1 closed+=4 tracked_fds=10 total=11 paused=false/false
Apr 18 02:14:18 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=0 hs_budget+=0 hs_timeout+=0 mp_fallback+=1
Apr 18 02:14:28 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=11 paused=false/false
Apr 18 02:14:38 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=11 paused=false/false
Apr 18 02:14:48 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=4/2000 hs_inflight=0 accepted+=0 closed+=1 tracked_fds=8 total=11 paused=false/false
Apr 18 02:14:50 renesmee mtproto-proxy[2432554]: warning(proxy): [11] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:14:58 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=1 closed+=0 tracked_fds=10 total=12 paused=false/false
Apr 18 02:14:58 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=0 hs_budget+=0 hs_timeout+=0 mp_fallback+=1
Apr 18 02:15:08 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=12 paused=false/false
Apr 18 02:15:18 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=12 paused=false/false
Apr 18 02:15:28 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=12 paused=false/false
Apr 18 02:15:38 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=1 closed+=1 tracked_fds=10 total=13 paused=false/false
Apr 18 02:15:43 renesmee mtproto-proxy[2432554]: warning(proxy): [13] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:15:48 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=1 closed+=1 tracked_fds=10 total=14 paused=false/false
Apr 18 02:15:48 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=0 hs_budget+=0 hs_timeout+=0 mp_fallback+=1
Apr 18 02:15:58 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=14 paused=false/false
Apr 18 02:16:08 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=14 paused=false/false
Apr 18 02:16:18 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=14 paused=false/false
Apr 18 02:16:27 renesmee mtproto-proxy[2432554]: warning(proxy): [14] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:28 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=1 closed+=1 tracked_fds=10 total=15 paused=false/false
Apr 18 02:16:28 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=0 hs_budget+=0 hs_timeout+=0 mp_fallback+=1
Apr 18 02:16:38 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=15 paused=false/false
Apr 18 02:16:39 renesmee mtproto-proxy[2432554]: warning(proxy): [15] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [16] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [17] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [18] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [19] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [34] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [42] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [22] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [23] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [28] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [37] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [35] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [33] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [38] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [45] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [31] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [30] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [24] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [32] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [21] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [27] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [40] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [20] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [43] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [36] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [39] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [47] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [54] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [44] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [41] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [26] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [55] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [62] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [65] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [69] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [29] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [67] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [70] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [74] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [25] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [52] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [64] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [72] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [46] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [51] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [49] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [68] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [56] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [58] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [71] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:44 renesmee mtproto-proxy[2432554]: warning(proxy): [61] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [76] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [77] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [80] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [78] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [82] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [79] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [92] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [98] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [83] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [91] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [81] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [90] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [84] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [89] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [94] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [93] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [95] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [104] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [100] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [96] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [88] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [85] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [99] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [102] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [101] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [86] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [87] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [105] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [103] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [57] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [66] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [97] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:45 renesmee mtproto-proxy[2432554]: warning(proxy): [63] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [117] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [106] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [110] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [108] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [109] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [116] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [107] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [115] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [112] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [111] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [121] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [122] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [119] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [120] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [114] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [124] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [118] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [123] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [125] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [113] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [126] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [127] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [129] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [130] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [128] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [131] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [133] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [132] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [134] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:46 renesmee mtproto-proxy[2432554]: warning(proxy): [135] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [136] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [137] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [138] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [139] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [140] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [142] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [143] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:47 renesmee mtproto-proxy[2432554]: warning(proxy): [141] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [144] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: info(proxy): conn stats: active=134/2000 hs_inflight=25 accepted+=148 closed+=19 tracked_fds=255 total=163 paused=false/false
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: info(proxy):   drops: cap+=0 sat+=0 rate+=109 hs_budget+=0 hs_timeout+=0 mp_fallback+=123
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [145] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [146] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [147] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [149] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [148] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [151] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [150] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [154] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [152] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [153] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [155] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [157] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [156] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [161] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [159] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [158] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [160] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [162] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [163] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [165] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [166] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [164] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [168] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [167] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [169] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [170] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [171] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [173] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:48 renesmee mtproto-proxy[2432554]: warning(proxy): [172] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [175] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [174] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [176] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [177] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [181] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [182] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [179] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [180] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [178] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [184] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [183] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [185] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [186] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [187] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [189] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [188] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [190] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [193] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [191] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [192] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [195] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [198] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [194] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [197] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [196] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [199] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [200] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [202] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [201] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:49 renesmee mtproto-proxy[2432554]: warning(proxy): [203] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [204] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [205] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [206] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [207] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [208] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [209] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [212] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [211] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [213] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [214] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [210] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [215] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [217] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [216] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [218] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [219] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [220] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [221] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [222] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [223] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [224] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [226] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [225] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [227] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [228] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [230] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [229] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [231] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [232] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:50 renesmee mtproto-proxy[2432554]: warning(proxy): [233] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [234] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [238] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [235] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [239] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [237] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [236] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [240] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [243] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [247] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [241] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [244] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [248] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [245] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [249] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [250] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [246] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [242] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [252] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [255] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [254] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [253] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [251] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [257] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [258] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [256] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Apr 18 02:16:51 renesmee mtproto-proxy[2432554]: warning(proxy): [259] middle-proxy handshake failed, reconnecting direct to [ipv4]:443

Diagnostics output

=== date ===
Sat Apr 18 10:18:48 UTC 2026

=== timedatectl ===
               Local time: Sat 2026-04-18 13:19:07 MSK
           Universal time: Sat 2026-04-18 10:19:07 UTC
                 RTC time: Sat 2026-04-18 10:19:07
                Time zone: Europe/Moscow (MSK, +0300)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

=== ulimit ===
1048576

=== ss ===
LISTEN 0      511        127.0.0.1:4433       0.0.0.0:*    users:(("nginx",pid=2399668,fd=5),("nginx",pid=2399667,fd=5),("nginx",pid=2399640,fd=5))
LISTEN 0      4096         0.0.0.0:443        0.0.0.0:*    users:(("mtproto-proxy",pid=2441333,fd=3))                                              
LISTEN 0      511          0.0.0.0:8443       0.0.0.0:*    users:(("nginx",pid=2399668,fd=8),("nginx",pid=2399667,fd=8),("nginx",pid=2399640,fd=8))

=== uname ===
Linux renesmee 6.12.74+deb13+1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.74-2 (2026-03-08) x86_64 GNU/Linux

=== memory ===
               total        used        free      shared  buff/cache   available
Mem:           3.8Gi       448Mi       2.8Gi       696Ki       805Mi       3.4Gi
Swap:          1.0Gi          0B       1.0Gi

=== systemctl ===
● mtproto-proxy.service - MTProto Proxy (Zig)
     Loaded: loaded (/etc/systemd/system/mtproto-proxy.service; enabled; preset: enabled)
     Active: active (running) since Sat 2026-04-18 03:21:07 MSK; 9h ago
 Invocation: 64d5d4d829054839b49960ff8298394e
       Docs: https://github.com/sleep3r/mtproto.zig
   Main PID: 2441333 (mtproto-proxy)
      Tasks: 2 (limit: 65535)
     Memory: 12.8M (peak: 31.3M)
        CPU: 38.609s
     CGroup: /system.slice/mtproto-proxy.service
             └─2441333 /opt/mtproto-proxy/mtproto-proxy /opt/mtproto-proxy/config.toml

Apr 18 13:19:30 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=7/2000 hs_inflight=0 accepted+=4 closed+=3 tracked_fds=14 total=7875 paused=false/false
Apr 18 13:19:40 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=7/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=14 total=7875 paused=false/false
Apr 18 13:19:50 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=7/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=14 total=7875 paused=false/false
Apr 18 13:20:00 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=7/2000 hs_inflight=0 accepted+=2 closed+=2 tracked_fds=14 total=7877 paused=false/false
Apr 18 13:20:10 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=7/2000 hs_inflight=0 accepted+=2 closed+=2 tracked_fds=14 total=7879 paused=false/false
Apr 18 13:20:20 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=7/2000 hs_inflight=0 accepted+=3 closed+=3 tracked_fds=14 total=7882 paused=false/false
Apr 18 13:20:30 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=8/2000 hs_inflight=0 accepted+=2 closed+=1 tracked_fds=16 total=7884 paused=false/false
Apr 18 13:20:40 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=8/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=16 total=7884 paused=false/false
Apr 18 13:20:50 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=3 tracked_fds=10 total=7884 paused=false/false
Apr 18 13:21:00 renesmee mtproto-proxy[2441333]: info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=10 total=7884 paused=false/false

Additional context

Отваливается MP (спонсорский канал пропадает) если я пускаю трафик через WG
Я пробовол разные теги подставлять как входного ip так и выходного. На 15 версии работало ещё.

Я хитро заворачиваю трафик в тунель (на самом сервере с MTPROTO у меня стоит сервер WG а не клиентский конфиг) а трафик выходит через удалённого клиента WG

Заворачивал ранее просто самого пользака mtproto правилами в тунель через ккастомную таблицу, сейчас добавил правило как появился режим tun и маркировка 200 в тунель.

чаты работают, всё прогружает, но хендшейк дропается.

Как только отключаю заворот через WG и отключаю fast_mode, всё начинает работать (мой хостер не блочит пока к DC телеграмма коннекты из РФ, вариант с пробросом через ру на перспективу)

В правилах iptables у меня так после старта тунеля:

# Generated by iptables-save v1.8.11 (nf_tables) on Sat Apr 18 13:29:03 2026
*mangle
:PREROUTING ACCEPT [949513:641301027]
:INPUT ACCEPT [949513:641301027]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [867911:835848271]
:POSTROUTING ACCEPT [867911:835848271]
-A FORWARD -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
-A OUTPUT -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
-A OUTPUT -p tcp -m tcp --sport 443 --tcp-flags SYN,ACK SYN,ACK -j TCPMSS --set-mss 88
COMMIT
# Completed on Sat Apr 18 13:29:03 2026
# Generated by iptables-save v1.8.11 (nf_tables) on Sat Apr 18 13:29:03 2026
*raw
:PREROUTING ACCEPT [949513:641301027]
:OUTPUT ACCEPT [867911:835848271]
COMMIT
# Completed on Sat Apr 18 13:29:03 2026
# Generated by iptables-save v1.8.11 (nf_tables) on Sat Apr 18 13:29:03 2026
*filter
:INPUT ACCEPT [949513:641301027]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [867911:835848271]
COMMIT
# Completed on Sat Apr 18 13:29:03 2026
# Generated by iptables-save v1.8.11 (nf_tables) on Sat Apr 18 13:29:03 2026
*nat
:PREROUTING ACCEPT [1161:70763]
:INPUT ACCEPT [1161:70763]
:OUTPUT ACCEPT [183:17202]
:POSTROUTING ACCEPT [180:17030]
-A POSTROUTING -o wg0 -j MASQUERADE
COMMIT
# Completed on Sat Apr 18 13:29:03 2026

Пояснить как работать с use_middle_proxy = true через WG и другой выходной ip?

[sleep3r]

Привет. Разобрался, проблема воспроизводима и не в коде - это ожидаемое поведение протокола middle-proxy при вашей схеме

Корень проблемы

Middle-proxy использует AES-ключи, выведенные через MD5/SHA1 из набора полей, среди которых есть IP-адрес самого прокси (так называемый clt_ip в getAesKeyAndIv - src/protocol/middleproxy.zig:38). Телеграм на своей стороне выводит те же ключи, но берёт clt_ip из accept() - то есть из реального src-IP TCP-соединения, которое он видит

У вас:

• use_middle_proxy = true
• Выход в мир через wg0 (сервер WG у тебя на машине с proxy, выходит клиент-пир)
• public_ip = 111.111.111.92 - это IP RU-сервера, на котором стоит сам прокси
• Но Телеграм видит коннекты от IP WG-пира

Прокси подставляет в вывод ключа 111.111.111.92, Телеграм подставляет IP WG-пира → ключи не совпадают → первый же зашифрованный кадр rpc_handshake не расшифровывается корректно → падает mp bad handshake ans type / mp bad handshake pid → fallback в direct (mp_fallback+=N в статах)

Чаты работают именно потому, что fallback-direct ходит без middle-proxy, а спонсорские каналы доступны только через middle-proxy, который и валится. Fast_mode тут лишь катализатор, т.к. без MP он работает по-другому пути

Посмотрите в логах:

info(proxy): Using server.public_ip for middle-proxy NAT translation: 111.111.111.92

Это и есть подстановка «неправильного» IP в ключ

Что нужно сделать

Добавьте в [server] явный IP, с которого реально выходит трафик в Телеграм (публичный IP удалённого WG-клиента, т.е. то, что видят сервисы типа curl ifconfig.me изнутри wg0):

[server]
public_ip = \"111.111.111.92\"          # твой RU-IP для клиентских tg:// ссылок
middle_proxy_nat_ip = \"<IP_WG_EXIT>\"  # реальный egress IP (то, что видит Telegram)

Ключи (public_ip, middle_proxy_nat_ip) именно для этого и разнесены - см. комментарий в src/config.zig:92-95:

Explicit IPv4 to use in Telegram MiddleProxy AES key derivation. Useful when public_ip is a domain name or when tunnel egress differs from generic "what is my IP" services

Как узнать <IP_WG_EXIT>:

# с сервера, внутри tunnel:
curl --interface wg0 https://api.ipify.org
# или маркированным сокетом:
curl --socks5 ... (или просто с хоста удалённого клиента)

Это должен быть тот же IP, что Telegram видит на TCP-accept - т.е. публичный IP того ноды, через которую у вас выходит wg-пир

Отдельная мелочь в логах

info(proxy): Upstream mode: direct (auto)

У вас в выложенном конфиге есть [upstream]\ntype = \"tunnel\", но лог пишет auto. Скорее всего реально в /opt/mtproto-proxy/config.toml на сервере этой секции нет (или сервис не перезапущен после её добавления). Вы маркируете трафик через iptables руками, поэтому оно всё равно идёт в wg0, но для чистоты:

1. Проверь cat /opt/mtproto-proxy/config.toml | grep -A1 '\\[upstream\\]'
2. systemctl restart mtproto-proxy после правок

При upstream.type = \"tunnel\" proxy сам ставит SO_MARK=200 на исходящие сокеты - это штатный путь вместо UID-based правил

Автодетект NAT-IP для чистого WG

Кстати, detectAwgEndpointIpv4 (src/proxy/proxy.zig:4154) парсит Endpoint = ... из wg0.conf. Но у вам на proxy-сервере - WG сервер, там в [Peer] секции Endpoint либо отсутствует, либо указывает на внутренний адрес клиента, а не на его публичный. Поэтому авто-детект корректно не сработает, и в вашем сценарии middle_proxy_nat_ip надо ставить руками

---

TL;DR: добавьте middle_proxy_nat_ip = \"<IP_через_который_wg_пир_ходит_в_интернет>\" в [server], перезапустите, и MP handshake пойдёт

[Guerrero3324]

Вчера долго пытался убрать эту ошибку, все же надо было спросить)
ВПС один, за границей, туда все и цепляются. Там же стоит амнезия, рядом.
Идет эта ошибка, медиа не грузится... Добавил туннель, на этот же сервер(у меня есть еще один комплект из двух впс РФ-ЕУ, прокси стоит в РФ, амнезия в ЕУ, туда туннель, там все нормально работает), все равно что то не так пошло, начал удалять этот туннель..
Кстати, установка туннеля есть из меню, а удалить нет))
В общем как то снес его... и все стало работать, ошибка пропала. Медиа грузятся... что сделал - не знаю)))

[quattro2h]

@Guerrero3324 Не подскажете как удалить туннель в проксе? Хочу потестить без него.

[quattro2h]

@sleep3r Александр, может вы подскажете как корректо удалить туннель?

[Guerrero3324]

@Guerrero3324 Не подскажете как удалить туннель в проксе? Хочу потестить без него.

Я ИИшке скормил вопросы и логи, он подсказал)

[d0bro]

Александр, спасибо за развернутый ответ.

Да, лог я дёрнул просто по памяти, тк в ночи сидел разбирался, и я разные просто схемы пробовал.

В выводе как раз тест когда я просто заворачивал через id польхака, соответственно настройка была старая, auto а не тунель.

Получается в боте мтпрото мне решать как выходной ip:port а не входящий?)

Ещё не показывает хелфтест nginx в дашборде, не копал.

Ну и добавил бы настройку path в дашборде, если например основной домен я на фейковый сайт веду, а директорию на дашборде с авторизацией (basic). Если так делать то пути ломается и обычным проксировпнием не обойтись, нужно либо в нджинкс фильтр писать или руками идти пути в шаблоне править.

[d0bro]

@sleep3r Проверил, работает. Единственное в логе при старте вот это и долго стартовал:

info(proxy): Upstream mode: tunnel (socket policy routing via SO_MARK=200)
info(proxy): Listening on 0.0.0.0:443 (epoll, single-thread)
info(proxy): Initial middle-proxy refresh unavailable (ConnectionTimedOut), using bundled defaults
info(proxy): conn stats: active=5/2000 hs_inflight=0 accepted+=57 closed+=52 tracked_fds=10 total=57 paused=false/false
info(proxy): drops: cap+=0 sat+=0 rate+=94 hs_budget+=0 hs_timeout+=0 mp_fallback+=0
info(proxy): conn stats: active=3/2000 hs_inflight=0 accepted+=0 closed+=2 tracked_fds=6 total=57 paused=false/false
info(proxy): conn stats: active=3/2000 hs_inflight=0 accepted+=0 closed+=0 tracked_fds=6 total=57 paused=false/false

Initial middle-proxy refresh unavailable - Вот это смущает.

И вопрос по звонкам, может обсуждался уже, почему-то звонок в ТГ не работает через mtproto
Пробовал у клиентов отключать pear-to-pear и включать, разные связки но не хочет. Это ожидаемо или у меня что-то не так?

[Guerrero3324]

У меня утром так же долго стартовал тот что в РФ и далее через туннель в EU, видимо обновления заползали долго...

А вот другой сервер который просто в EU и без туннеля...
Upstream mode: direct (auto)
info(proxy): Listening on [::]:443 (epoll, single-thread)
info(proxy): Initial middle-proxy refresh unavailable (UnexpectedConnectFailure), using bundled defaults
info(proxy): Middle-proxy early retry unavailable (UnexpectedConnectFailure), will try again

[d0bro]

Также вот чекер ломается, может просто curl ifconfig.me дёргать или пинг до 1.1.1.1 переодисччески через тунель чтобы подсвечивать что тунель активен в дашборде.

[d0bro]

В 0.19.2 что-то поломалось совсем

info(proxy): Middle-proxy asset https://core.telegram.org/getProxyConfig unreachable directly (ConnectionTimedOut); retrying via tunnel 'wg0'

И нет коннекта к проксе совсем.

[d0bro]

@sleep3r что-то с маркировкой пакетов, вернул свой конфиг WG на котором просто заворачиваю так:

# === ПРАВИЛА ПРИ ЗАПУСКЕ ===

# 1. Гарантия доступности SSH и ответов прокси: 
# Если пакет идет С нашего IP, он ВСЕГДА идет в основную таблицу (мимо туннеля)
PostUp = ip rule add from 192.168.0.73 table main priority 100

# 2. Магия UID: Весь исходящий трафик от пользователя mtproto (UID 999) заворачиваем в туннель
PostUp = ip rule add uidrange 999-999 table mtg_table priority 200
PostUp = ip route add default dev %i table mtg_table

# 3. NAT (Masquerade) для пакетов, уходящих в туннель
PostUp = iptables -t nat -A POSTROUTING -o %i -j MASQUERADE
PostUp = iptables -t mangle -I PREROUTING -p tcp --dport 443 --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1200

# 4. Фикс MTU/MSS (Критично для Telegram):
# Заставляем TCP пакеты "сжиматься", чтобы они пролезали в туннель без фрагментации
# Делаем это и для транзита (FORWARD), и для локально созданных пакетов (OUTPUT)
PostUp = iptables -t mangle -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
PostUp = iptables -t mangle -I OUTPUT -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu

# 5. Сброс старых соединений (на всякий случай)
PostUp = conntrack -F

# === ОЧИСТКА ПРИ ОСТАНОВКЕ ===
PreDown = ip rule del from 192.168.0.73 table main priority 100 || true
PreDown = ip rule del uidrange 999-999 table mtg_table priority 200 || true
PreDown = ip route del default dev %i table mtg_table || true
PreDown = iptables -t nat -D POSTROUTING -o %i -j MASQUERADE || true
PreDown = iptables -t mangle -D PREROUTING -p tcp --dport 443 --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1200 || true
PreDown = iptables -t mangle -D FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu || true
PreDown = iptables -t mangle -D OUTPUT -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu || true

И сразу заработало:

⏳ Waiting for connections...
info(proxy): mask_port=4433 configured, using local mask target 127.0.0.1
info(proxy): Mask target '127.0.0.1:4433' resolved at startup
info(proxy): Using server.middle_proxy_nat_ip for middle-proxy NAT translation: тут внешний ip WireGuard)
info(proxy): Upstream mode: direct (auto)
info(proxy): Listening on 0.0.0.0:443 (epoll, single-thread)
info(proxy): Middle-proxy cache updated: dc4=.{ .any = .{ .family = 2, .data = { 34, 184, 91, 108, 4, 164, 0, 0, 0, 0, 0, 0, 0, 0 } }, .in = .{ .sa = .{ .family = 2, .port = 47138, .addr = 2751753307, .zero = { ... } } }, .in6 = .{ .sa = .{ .family = 2, .port = 47138, .flowinfo = 2751753307, .addr = { ... }, .scope_id = 0 } }, .un = .{ .family = 2, .path = { 34, 184, 91, 108, 4, 164, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } } } dc203=.{ .any = .{ .family = 2, .data = { 1, 187, 91, 105, 192, 110, 0, 0, 0, 0, 0, 0, 0, 0 } }, .in = .{ .sa = .{ .family = 2, .port = 47873, .addr = 1858103643, .zero = { ... } } }, .in6 = .{ .sa = .{ .family = 2, .port = 47873, .flowinfo = 1858103643, .addr = { ... }, .scope_id = 0 } }, .un = .{ .family = 2, .path = { 1, 187, 91, 105, 192, 110, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } } } secret_len=128
info(proxy): conn stats: active=1/1150 hs_inflight=0 accepted+=1 closed+=0 tracked_fds=2 total=1 paused=false/false
info(proxy): Middle-proxy cache updated: dc4=.{ .any = .{ .family = 2, .data = { 34, 184, 91, 108, 4, 161, 0, 0, 0, 0, 0, 0, 0, 0 } }, .in = .{ .sa = .{ .family = 2, .port = 47138, .addr = 2701421659, .zero = { ... } } }, .in6 = .{ .sa = .{ .family = 2, .port = 47138, .flowinfo = 2701421659, .addr = { ... }, .scope_id = 0 } }, .un = .{ .family = 2, .path = { 34, 184, 91, 108, 4, 161, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } } } dc203=.{ .any = .{ .family = 2, .data = { 1, 187, 91, 105, 192, 110, 0, 0, 0, 0, 0, 0, 0, 0 } }, .in = .{ .sa = .{ .family = 2, .port = 47873, .addr = 1858103643, .zero = { ... } } }, .in6 = .{ .sa = .{ .family = 2, .port = 47873, .flowinfo = 1858103643, .addr = { ... }, .scope_id = 0 } }, .un = .{ .family = 2, .path = { 1, 187, 91, 105, 192, 110, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } } } secret_len=128

[Frew777]

@sleep3r
А как с этим быть? Туннель AWG

# curl --interface awg0 ifconfig.co
104.28.198.242
# curl --interface awg0 https://api.ipify.org
104.28.198.242
# curl --interface awg0 https://ifconfig.me
104.28.198.244

Вообще не подключается к ME

# journalctl -u mtproto-proxy.service -f
Jul 07 03:32:33 test1 mtproto-proxy[46669]:   ─── SECURITY ───────────────────────────────────
Jul 07 03:32:33 test1 mtproto-proxy[46669]:       User secrets and proxy links are hidden in runtime logs.
Jul 07 03:32:33 test1 mtproto-proxy[46669]:       Use mtbuddy install output or trusted local tooling to generate links.
Jul 07 03:32:33 test1 mtproto-proxy[46669]:   ──────────────────────────────────────────────────
Jul 07 03:32:33 test1 mtproto-proxy[46669]:   ⏳ Your door is open. Waiting for the people you love...
Jul 07 03:32:33 test1 mtproto-proxy[46669]: info(proxy): mask_port=8443 configured, using local mask target 127.0.0.1
Jul 07 03:32:33 test1 mtproto-proxy[46669]: info(proxy): Mask target '127.0.0.1:8443' resolved at startup
Jul 07 03:32:34 test1 mtproto-proxy[46669]: info(proxy): Detected egress public IPv4 for middle-proxy NAT translation: 104.28.198.242 (upstream=tunnel)
Jul 07 03:32:34 test1 mtproto-proxy[46669]: info(proxy): Upstream mode: tunnel (socket policy routing via SO_MARK=200)
Jul 07 03:32:34 test1 mtproto-proxy[46669]: info(proxy): Listening on [::]:443 (epoll)

Всегда эта ошибка

warning(proxy): [0] middle-proxy handshake failed, reconnecting direct to [ipv4]:443

Пробовал и вручную указать middle_proxy_nat_ip, и автоматически он правильно получает. Но коннекта к middle_proxy - нету.

Вот конфиг

[server]
port = 443
max_connections = 512
idle_timeout_sec = 120
handshake_timeout_sec = 15
handshake_flood_guard_enabled = false
handshake_flood_guard_threshold = 20
handshake_flood_guard_window_sec = 30
handshake_flood_guard_block_sec = 120
#public_ip = "***"
#middle_proxy_nat_ip = "104.28.198.242"
#middle_proxy_nat_ip = "104.28.198.244"

[upstream]
type = "tunnel"

[censorship]
tls_domain = "rutube.ru"
mask = true
desync = false
drs = false
fast_mode = true

mask_port = 8443
[general]
use_middle_proxy = true

[access.users]
user = "c85fcd0b63d0a1e6a016c95f6364852b"


[upstream.tunnel]
interface = "awg0"
interfaces = ["awg0"]

В один момент я подумал, что может подключение к middle_proxy идёт через IPv6, отключил его в конфиге awg0.conf, но ситуацию это не изменило.