TxThinking

tested on new, clean, genuine version of Windows 10 and 11. need more information to reproduce your issue

v20240606 released

## UDP addr：监听地址 ip: socks5 server 真正的 IP。 **因为 socks5 server 的 UDP 地址是：当客户端向服务端询问的时候，需要由服务端告诉客户端的，所以你得先告诉服务端程序应该告诉客户端什么。记住这句话** 有两种情况。有NAT和无NAT的环境。 ## 无NAT环境： 比如你买了一个机器。公网IP是 1.2.3.4。此时你进入机器，你会发现网卡上的确绑定了 1.2.3.4。 就可以直接 addr 为 1.2.3.4:1080，ip 为 1.2.3.4。最终客户端使用的时候就是 1.2.3.4:1080 **这时当客户端向服务端询问UDP 地址时，程序就需要告诉客户端，也就是这个 ip，...

Section 7: `The UDP relay server *MUST* acquire from the SOCKS server the expected IP address of the client that will send datagrams to the BND.PORT given in the reply...

@yinghuocho > Yes, I also noticed that shadowsocks-libev's UDP relay does not comply with the RFC. It closes UDP Associate's corresponding TCP connection prematurely. After I commented a few lines...

v20240923

根据这里描述 https://ubuntu.com/server/docs/security-trust-store 可尝试如下： ``` sudo apt-get install -y ca-certificates sudo cp ~/.nami/bin/ca.pem /usr/local/share/ca-certificates/ca.crt sudo update-ca-certificates ```

https://microsoftedge.microsoft.com/addons/detail/makcfnkaapoandbeldfnmamikefoafao