UDP trackers resolving to IPv6 on IPv4 only system

[autogris]

libtorrent version (or branch): 2.0.11 (24e658a)

platform/architecture: Linux x86_64

compiler and compiler version: gcc 14.2.0

please describe what symptom you see, what you would expect to see instead and
how to reproduce it.

I'm running libtorrent through a SOCKS5 proxy, checking the proxy logs it shows that UDP connections are resolving to ipv6 address, but neither the client nor the server have ipv6 enabled, so the connection fails. The client side (tried with Deluge and qBittorent) resolves the hostname locally not through the proxy/server. Is there any settings or workaround to force libtorrent resolve to ipv4? Curiously, TCP connections uses ipv4 correctly.

[arvidn]

checking the proxy logs it shows that UDP connections are resolving to ipv6 address

What do you mean by a "connection" resolving to an address? Typically hostnames resolve to IP addresses. If you have a hostname to a UDP tracker that resolves to an IPv6 address, I would guess that it also resolves to an IPv4 address. libtorrent will attempt to contact the IPv6 address. If that fails, move down the list of resolved IPs and try those.

Is that not happening?
Is the hostname resolving only to an IPv6 address?

SOCKS5 supports talking to peers by just specifying their hostname, letting the proxy resolve it to an IP address. Is that your scenario, where the proxy is resolving it to IPv6 and then failing?