My objective is to make associate UDP works with the radius auth. Each of these two works for me if I'm using them independently. Thanks in advance!
OS:Ubuntu 22.04.4 LTS
3proxy-0.9.4(from GitHub Release DEB)

Option #1 - radius only.
Radius auth works good. TCP over socks5 works good. Associate UDP doesn't work

240418164442.632 1090 00000 greg 95.161.221.176:61715 194.76.46.8:443 493 3114 0 CONNECT api.datascrape.tech:443
240418163009.438 1090 00012 greg 95.161.221.176:60337 0.0.0.0:0 0 0 0 UDPMAP 0.0.0.0:0

There are plenty of available unprivileged ports for new UDP sockets.

nscache 65536
nserver 8.8.8.8
nserver 8.8.4.4

config /conf/3proxy.cfg
monitor /conf/3proxy.cfg

log /logs/3proxy-%y%m%d.log D
rotate 60
counter /count/3proxy.3cf

users $/conf/passwd

include /conf/counters
include /conf/bandlimiters

radius iddqd 127.0.0.1
authcache user,password 10

internal 10.20.30.40
external 10.20.30.40
noforce
auth radius
#auth cache radius
#auth strong
allow * * * * *
socks -p1090
flush

Option #2 - local password auth.
If I change line no.23 from auth radius to auth strong both TCP and UDP over socks5 work good

240418162700.843 1090 00004 greglocal 95.161.221.176:60067 0.0.0.0:0 0 0 0 UDPMAP 0.0.0.0:0

Option #3 - radius with the cache
If I change line no.23 from auth radius to auth cache radius  I see counterintuitive behavior. If 1st request after config reload is associate UDP - it doesn't work with the same 12 error code. If the 1st request is TCP over socks5 - it works good and even more, the next associate UDP requests works also good in the next 10s(equal to the cache lifetime)