Hi Remnawave team,
Could you add support for configuring ECH (Encrypted Client Hello) per host/domain?
Currently, one inbound can have multiple hosts, for example 10 different hosts with 10 different domains, but there doesn’t appear to be a way to configure ECH individually for each host.
For example:
{
"serverName": "domain.com",
"echConfig": "udp://8.8.8.8"
}
The ideal implementation would be to add an ECH configuration field inside the Hosts configuration UI, so each host can independently have ECH enabled or disabled.
For example:
Host 1
Domain: domain1.com
ECH: udp://1.1.1.1
Host 2
Domain: domain2.com
ECH: Disabled
Host 3
Domain: domain3.com
ECH: udp://1.1.1.1
This is important because ECH may only be needed for some hosts, while others may not require it.
Also, when using Cloudflare, we don’t need to configure ECH server-side in the Xray inbound. The important part is the client-side ECH configuration. Remnawave could therefore simply add the ECH parameter to the generated client/subscription configuration for the specific hosts where it is enabled.
For example, the generated VLESS link could look like:
vless://[email protected]:443?encryption=none&security=tls&sni=Domain.com&fp=chrome&alpn=http%2F1.1&insecure=0&allowInsecure=0&ech=udp%3A%2F%2F8.8.8.8&type=ws&host=Domain.com&path=%2F#Ech%20vless%20example%20with%20Ech
The important parameter is:
ech=udp://8.8.8.8
So if ECH is enabled for a particular host, Remnawave would automatically add:
ech=udp://8.8.8.8
to that host’s generated VLESS configuration. If ECH is disabled for that host, the parameter would simply be omitted.
This would allow a single inbound to have multiple domains while giving us independent ECH configuration per host, without having to modify the Xray JSON and unintentionally apply ECH to all hosts.
Thank you.