Inbound tags/prefixes are broken during subscription routing export (Causes EOF / illegal domain rule errors in client app)

Автор: f******@mail.ru

Продукт: Приложение INCY

Создан: 26.08.2026, 20:58:07

When exporting routing rules via the subscription link, the 3X-UI panel automatically parses and modifies custom geodata routing rules inside the rules array.
During this conversion, it strips file prefixes from rules like "ext:geosite_roscom.dat:torrent", converting them into a simplified format like "geosite:torrent".This behavior completely breaks client applications (such as INCY or Infly) because their internal Xray/V2Ray core attempts to locate the rule within the standard geosite.dat file instead of the custom .dat file specified by the user.

As a result, the client app fails to parse the config and throws critical errors, blocking the VPN connection entirely: i_nfra/conf/serial: failed to parse json config > ... > illegal domain rule: geosite:torrent > ... > EOF_
Additionally, the converter seems to cause issues with case sensitivity or hyphens on some tags (e.g., breaking down specific ad-blocking or custom rules like converting geosite:twitch-ads into broken tags).

Steps to Reproduce:
Add a custom geodata rule to the 3X-UI routing template or inbound routing settings using a specific file prefix, for example: "ext:geosite_roscom.dat:torrent".
Generate a subscription link for a user and import it into a client application that processes subscription routing (like INCY).
Observe that the exported base64 config contains "geosite:torrent" instead of preserving the explicit "ext:geosite_roscom.dat:torrent" path.
The client application fails to start the core with a geodata parsing EOF error.
Expected Behavior:
The subscription export mechanism should preserve explicit file prefixes (ext:filename.dat:tag) inside the routing rules array "as is", without attempting to strip or simplify them into standard geosite: / geoip: domains, or it should provide an option to disable rule optimization for advanced subscription templates.

Actual Behavior:
The panel optimizes/simplifies the tags during export, stripping out custom .dat references, which causes a mismatch and crashes the Xray core on the client side.

Environment:
3X-UI Version: 3.6.0
Xray Core Version: 26.7.28
Client App: INCY iOS