

You will not be able to enable legacy header workaround in the future. You can still disable this security feature with environment variable v2ray. 225: 55865 rejected common / drain: common / drain: unable to drain connection > EOF > proxy / vmess / encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received. 225: 55827 rejected common / drain: common / drain: unable to drain connection > transport / internet / kcp: Read / Write timeout > proxy / vmess / encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received.

com / core / proxy / socks: connection ends > context canceled

com / core / app / proxyman / inbound: connection ends > v2ray. com / core / proxy / vmess / outbound: connection ends > context canceled 2022 / 01 / 16 22: 45: 31 v2ray. com / core / app / proxyman / outbound: failed to process outbound traffic > v2ray. com / core / transport / internet / kcp: # 30685 closing connection to 192.248.

com / core / proxy / socks: connection ends > context canceled 2022 / 01 / 16 22: 45: 31 v2ray. com / core / proxy / vmess / outbound: connection ends > context canceled 2022 / 01 / 16 22: 45: 21 v2ray. com / core / transport / internet / kcp: # 30679 closing connection to 192.248. com / core / proxy / socks: connection ends > context canceled 2022 / 01 / 16 22: 45: 20 v2ray. 225: 55865 > common / drain: common / drain: unable to drain connection > EOF > proxy / vmess / encoding: invalid user: VMessAEAD is enforced and a non VMessAEAD connection is received.
