Using SOCKS5 proxy (squid) doesn't work

[ell1e]

I've managed to make my browser use a squid proxy, reachable through localhost 3129, but I can't get dnscrypt-proxy to work using this setup:

# cat /etc/dnscrypt-proxy/dnscrypt-proxy.toml | grep -E "(socks5|tcp)"
force_tcp = true
## Tor doesn't support UDP, so set `force_tcp = true
## a random username and password to Tor's socks5 connection, dnscrypt-proxy gets
#proxy = 'socks5://dnscrypt:dnscrypt@127.0.0.1:9050'
proxy='socks5://127.0.0.1:3129'

Any attempt to resolve a name just fails:

# ping google.com
ping: bad address 'google.com'
#

This is what the log says:

# cat /var/log/dnscrypt-proxy/dnscrypt-proxy.log 
[2026-01-17 03:47:57] [NOTICE] dnscrypt-proxy 2.1.14
[2026-01-17 03:47:57] [NOTICE] Using default Weighted Power of Two (WP2) load balancing strategy
[2026-01-17 03:47:57] [NOTICE] Network connectivity detected
[2026-01-17 03:47:57] [NOTICE] Now listening to [::]:53 [UDP]
[2026-01-17 03:47:57] [NOTICE] Now listening to [::]:53 [TCP]
[2026-01-17 03:47:57] [NOTICE] Source [relays] loaded
[2026-01-17 03:47:57] [NOTICE] Source [public-resolvers] loaded
[2026-01-17 03:47:57] [NOTICE] Firefox workaround initialized
[2026-01-17 03:47:57] [NOTICE] Hot reload is disabled
[2026-01-17 03:48:07] [ERROR] Get "https://adblock.dns.mullvad.net/dns-query?dns=<redacted>": context deadline exceeded
[2026-01-17 03:48:07] [NOTICE] dnscrypt-proxy is waiting for at least one server to be reachable

When I have a wifi available where no SOCKS5 proxy is needed for access, dnscrypt-proxy works perfectly fine. So this seems to be some proxy handling related issue.

Does anybody have an idea what might be going on?

[jedisct1]

Squid is not a SOCKS proxy.