Hi, I would like to request support for standalone/serverless client profiles in subscription output.
Currently, hosts seem to be generated around a normal proxy outbound/inbound model, such as VLESS/TCP/Reality. This works fine for regular nodes, but it makes it hard or impossible to add a client-only profile that does not connect to any server.
Use case:
I want to add a selectable profile like:
- Istanbul
- Frankfurt
- Fragment / Serverless Bypass
The Fragment / Serverless Bypass profile should not connect to any PasarGuard node. It should only use local Xray client features such as:
mixed, socks, http, or DNS inbounds
freedom outbound
- TCP TLS fragment
- UDP noises
- FakeDNS
- custom routing rules
When I try to use a standalone Xray client template for this, the subscription output/client becomes broken and all nodes show as N/A in client. It looks like the host system expects a generated proxy outbound and does not support a fully custom standalone client profile.
Requested feature:
Please allow us to add inbounds such as mixed, socks, http, or DNS inbounds to the hosts., for example:
This profile should:
- Be shown as a selectable item in the subscription, like a normal host.
- Not require a real server/node address.
- Not inject a generated proxy outbound unless explicitly enabled.
- Allow full custom client JSON, including custom inbounds/outbounds/routing/DNS/FakeDNS.
This would make it possible to offer serverless censorship-bypass modes, such as Xray fragment/noise based profiles, alongside normal VPN nodes in the same subscription.
Thanks.
Hi, I would like to request support for standalone/serverless client profiles in subscription output.
Currently, hosts seem to be generated around a normal proxy outbound/inbound model, such as VLESS/TCP/Reality. This works fine for regular nodes, but it makes it hard or impossible to add a client-only profile that does not connect to any server.
Use case:
I want to add a selectable profile like:
The
Fragment / Serverless Bypassprofile should not connect to any PasarGuard node. It should only use local Xray client features such as:mixed,socks,http, or DNS inboundsfreedomoutboundWhen I try to use a standalone Xray client template for this, the subscription output/client becomes broken and all nodes show as N/A in client. It looks like the host system expects a generated proxy outbound and does not support a fully custom standalone client profile.
Requested feature:
Please allow us to add inbounds such as mixed, socks, http, or DNS inbounds to the hosts., for example:
This profile should:
This would make it possible to offer serverless censorship-bypass modes, such as Xray fragment/noise based profiles, alongside normal VPN nodes in the same subscription.
Thanks.