Skip to content
Discussion options

You must be logged in to vote

That's freedom's default safety policy. When traffic comes in through a VLESS, VMess, Trojan, Shadowsocks, Hysteria or WireGuard inbound and no finalRules entry matches, freedom blocks private/reserved IPs (including 127.0.0.1) and blackholes the connection. That's the blocked target ... blackholing connection line.

Add an explicit allow rule on the remote server's freedom outbound. Rules are checked in order before the default:

{ "protocol": "freedom", "settings": { "finalRules": [ { "action": "allow", "network": "udp", "ip": ["127.0.0.1/32"] } ] } }

You can also add "port": "" to keep the hole as small as possible.

Docs: https://xtls.github.io/en/config/outbounds/freedom.html (see final…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@pstreem
Comment options

Answer selected by pstreem
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants