Routing by domains don't work #4653
Replies: 3 comments 2 replies
-
I can't reproduce it. Have you tried building xray from latest source? "tag": "inbound-31842",
"sniffing": {
"enabled": false,
"destOverride": [
"http",
"tls",
"quic",
"fakedns"
],
"metadataOnly": false,
"routeOnly": false
}, Also, is the setting of |
Beta Was this translation helpful? Give feedback.
-
I have the same issue with wireguard inbound. From the logs I can see that my local xray server recognizes the domain names of the requests from my socks inbound but for wg it only sees the ip addresses. I don't know if this can be fixed by configuration. Although IP based routing should still work. |
Beta Was this translation helpful? Give feedback.
-
Can confirm all the domain rules are ignored in my case too:
Visiting 2ip.ru directly ignores routing rules altogether and goes straight to the first entry in outbounds:
Routing by IP works fine:
results in
|
Beta Was this translation helpful? Give feedback.
-
Hello. I installed and configured X-ray by x-ui. I have following scheme:
router connected by wireguard (inbound named as inbound-26675) to local X-ray installed on raspberry pi. X-ray on that raspberry should route my ru-traffic to the direct outbound and all other traffic to remote x-ray installed on vps (named in config as is_vmess). This scheme worked for some time but has been broken a months ago after upgrading xray. Now all traffic included ru from wireguard (and from other inbounds I tested as in this config) routed to one destination (is_vmess) and ignore domain routing. I waited for a months by upgrading xray for a fix, but it still not working. May be you can help me what wrong with my config or so.
By this config only this route rule works
This part was generated by x-ui from the web interface:
Beta Was this translation helpful? Give feedback.
All reactions