[Bug Report] WireProxy Does Not Automatically Fallback to IPv6 When IPv4 Connection Fails

[CellLz]

[Bug Report] WireProxy Does Not Automatically Fallback to IPv6 When IPv4 Connection Fails

English Version

Problem Description

When running WireProxy on a server that only has IPv6 connectivity, if the endpoint address in the WireGuard configuration file is a dual-stack domain name (e.g., engage.cloudflareclient.com), WireProxy always attempts to connect to the IPv4 address first (e.g., 162.159.192.1). Since the server lacks IPv4 connectivity, the connection inevitably fails.

However, when I manually set the endpoint to the corresponding IPv6 address (e.g., 2606:4700:d0::a29f:c001), the connection succeeds immediately.

Suggestion

It would be beneficial for WireProxy to implement a fallback mechanism. If the initially resolved IP address cannot establish a connection, the program should automatically try the next resolved IP, whether it is IPv4 or IPv6. This behavior would improve compatibility in environments with partial connectivity.

Thank you for your consideration and for maintaining such an excellent project!

---

中文版本

问题描述

在仅有 IPv6 网络的服务器上运行 WireProxy 时，如果 WireGuard 配置文件中的 endpoint 地址是双栈域名（例如 engage.cloudflareclient.com），WireProxy 总是优先尝试连接 IPv4 地址（如 162.159.192.1）。由于服务器没有 IPv4 网络，连接必然失败。

但当我手动将 endpoint 修改为对应的 IPv6 地址（如 2606:4700:d0::a29f:c001）后，连接立即成功。

建议

建议 WireProxy 实现一个自动回退机制：如果解析出的第一个 IP 无法连接，程序应自动尝试下一个解析出的 IP（无论是 IPv4 还是 IPv6）。此功能将在存在网络连接限制的环境中显著提高兼容性。

感谢您的关注，也感谢您开发和维护如此优秀的项目！