#6570 [Bug]: Awg outbound can't connect to the server

Describe the bug

I wanted to try out awg outbound and stuck with the issue of not being able to connect to the server. On my Keenetic router and android everything works as intended. I thought that as based on awg documentation if I were to delete I1 then system would fallback to awg 1.0 or 1.5 implementation but even that didn't help. Routing itself works via xray, I can see that outbound works on my awg easy server panel but 50 percent of the time probing the http or real delay results in fail.

And right after this failed attempt:

I got suspicious since there no I2 to I5 parametrs and only I1 available in the UI. Is that an intended behaviour?

No I2 to I5 which I can specify and I assume that's why server fails to response properly

Also I don't quite understand why it's using Ipv6 if I excplicitely used Ipv4 in my configuration and even if used domain could it realize that ipv6 is unavailable and fallback to ipv4? (See the logs)

How to reproduce the problem

Create an awg outbound
Probe the outbound using built-in HTTP or Real Delay
See probing resulted in 50/50 percent chance of being dropped or failed

Expected behavior

No response

Actual behavior

No response

Relevant logs

WARNING - X-UI: amneziawgnet: egress "awg": dial tunnel [2001:4860:4826:7700::]:443: connect tcp [2001:4860:4826:7700::]:443: network is unreachable
2026/09/16 14:01:02 WARNING - XRAY: core: Xray 26.9.9 started
2026/09/16 14:01:02 WARNING - XRAY: proxy/wireguard: Using gVisor TUN

Screenshots

No response

3x-ui version

3.8.5

Xray-core version

25.9.9

How did you install 3x-ui?

install.sh script

Operating system

docker

Which parts of the panel are affected?

No response

Browser (only if it is a UI bug)

No response

Is the panel behind a reverse proxy or CDN?

None

Before submitting

I searched existing issues and this bug has not been reported.
I am running the latest released version of 3x-ui (or have verified the bug still exists on it).
This bug report is written in English.
I have redacted any sensitive data (tokens, real domains, client UUIDs).