Hello, I'm faced with a blocking issues using the wireproxy-awg with an amnezia 2.0.
May 22 14:54:51 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:54:51 peer(ZS0Y…GbW8) - Handshake did not complete after 5 seconds, retrying (try 2)
May 22 14:54:51 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:54:51 peer(ZS0Y…GbW8) - Sending handshake initiation
May 22 14:54:57 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:54:57 peer(ZS0Y…GbW8) - Handshake did not complete after 5 seconds, retrying (try 2)
May 22 14:54:57 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:54:57 peer(ZS0Y…GbW8) - Sending handshake initiation
May 22 14:55:02 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:55:02 peer(ZS0Y…GbW8) - Sending handshake initiation
May 22 14:55:07 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:55:07 peer(ZS0Y…GbW8) - Sending handshake initiation
May 22 14:55:12 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:55:12 peer(ZS0Y…GbW8) - Handshake did not complete after 5 seconds, retrying (try 2)
May 22 14:55:12 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:55:12 peer(ZS0Y…GbW8) - Sending handshake initiation
May 22 14:55:17 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:55:17 peer(ZS0Y…GbW8) - Handshake did not complete after 5 seconds, retrying (try 2)
May 22 14:55:17 camholder wireproxy[1255]: DEBUG: 2026/05/22 14:55:17 peer(ZS0Y…GbW8) - Sending handshake initiation
But, the original (IOS) client still works well.
Seems, the original client use some additional anti-blocking tricks not implemented at wireproxy?
May be you may help to solve this issues?
Of course, the wireproxy is only about the wireguard, but, AFAIU, protocols are similar.
The problem may be with some markers that anti-DPI systems perceive as "wireguard" (which is fully blocked) even when amnezia protocol is used and wireproxy-awg should change them?
Hello, I'm faced with a blocking issues using the wireproxy-awg with an amnezia 2.0.
But, the original (IOS) client still works well.
Seems, the original client use some additional anti-blocking tricks not implemented at wireproxy?
May be you may help to solve this issues?
Of course, the wireproxy is only about the wireguard, but, AFAIU, protocols are similar.
The problem may be with some markers that anti-DPI systems perceive as "wireguard" (which is fully blocked) even when amnezia protocol is used and wireproxy-awg should change them?