К содержимому
INCY
Назад

Domain blocking in routing profiles does not work in TUN + Proxy mode

БагОткрытМешаетПубличныйAndroid
Автор: n*******@gmail.com
Продукт: Приложение INCY
Создан: 15.10.2026, 17:29:50
Версия приложения: 3.7.0
Версия ОС: 15 AP3A.240905.015.A2
Модель устройства: Redmi 22
Platform: Android
App: INCY
Tunnel mode: TUN + Proxy
Advanced routing profiles: Enabled
Domain routing (routeOnly): Enabled
FakeDNS: Disabled
DNS: Cloudflare DoH ("https://cloudflare-dns.com/dns-query") and Google DNS ("8.8.8.8")

Problem

I added the following rules to my active, default routing profile:

- "domain:astronautlividlyreformer.com"
- "geosite:category-ads"

The profile is enabled and is the first and default profile in the list. The routing order is "block-direct-proxy", and global proxy mode is enabled.

However, when I open a website in Chrome that redirects to "astronautlividlyreformer.com", the redirect is not blocked.

I enabled Debug logging, reproduced the problem while the VPN was connected, disconnected the VPN, and examined the session log. The log contains other Xray connections and entries such as "sniffed domain", but I could not find the target domain or any evidence that its connection was blocked.

Questions

1. Does INCY merge the rules from the active routing profile into the server's imported Xray configuration, or can the server configuration override or bypass those profile rules?
2. Is "domain:astronautlividlyreformer.com" the correct syntax for blocking this domain in the routing profile?
3. Are there known limitations with domain blocking in TUN + Proxy mode, particularly for Chrome HTTPS or QUIC connections?
4. How can I verify that a domain-blocking rule is actually loaded and applied, without access to the internal Xray configuration?

I can provide the exported server configuration and a redacted Debug log if needed.

Expected behavior: Connections to "astronautlividlyreformer.com" should be blocked by the active routing profile.

Actual behavior: The redirect still occurs, and the log does not show the target domain or a matching block action.
Комментарии (1)
n*******@gmail.com15.10.2026, 17:33:35
... 
Добавить комментарий