Closed alexsammers1 closed 1 month ago
Quick Note - the Custom Routing
stops the server from connecting, if you have any routing rules added to the file.
If it's blank/default option - works fine.
It seems like the app stopped recognizing the routing rules, even if they're added correctly - in my case, copied directly from 3X-UI Panel.
Update - found the issue. As soon as you add the Routing Rule
with geosite
, it stops connecting with the error above, e.g.
{
"type": "field",
"outboundTag": "direct",
"domain": [
"geosite:category-ru",
"regexp:.*\\.ru$"
]
}
]
}
Solution - remove geosite
and just leave regexp
, e.g.
{
"type": "field",
"outboundTag": "direct",
"domain": [
"regexp:.*\\.ru$"
]
}
]
}
[2024-09-24 14:14:04,849] [Furious.QtFramework.CoreProcess] [ERROR] Xray-core stopped unexpectedly with exitcode 23
Hi. If Xray-core exited with code 23 it means that the configuration is invalid. It can happen if the geo asset file is not found, bad config, etc.
Roger - thank you 🤝
Hey Everybody!
I've just updated the
3X-UI
tov2.4.1
andXray
tov24.9.19
, and the app no longer works withCustom Routing
option enabled. I've tried with previous/currentXray
tov1.8.23
- same result. It tries to connect, but then fails.Log:
If you choose any other option, e.g.
Global Routing
- no issues, connected successfully.What could be the issue here? Do I need to revert the
3X-UI
to a previous version, or does something need to be updated in the app?