hiddify / hiddify-next

Multi-platform auto-proxy client, supporting Sing-box, X-ray, TUIC, Hysteria, Reality, Trojan, SSH etc. It’s an open-source, secure and ad-free.
https://hiddify.com
Other
15.81k stars 1.45k forks source link

VLESS Node Timeout and DNS Resolution Failure in Hiddify #1352

Closed NebulaTechs closed 4 hours ago

NebulaTechs commented 6 hours ago

Search first

What Happened?

I am experiencing an issue where my VLESS node (using port 443) works perfectly in v2rayNG but times out and fails DNS resolution in Hiddify. The error message I receive is:

dns:exchange failed for https://example.org/ IN A:context canceled

Minimal Reproducible Example (MRE)

  1. Configure the VLESS node in v2rayNG and verify that it works correctly.
  2. Configure the same VLESS node in Hiddify.
  3. Attempt to connect using Hiddify.
  4. Observe the timeout and DNS resolution failure.

Expected Behavior

The VLESS node should work correctly in Hiddify, similar to how it works in v2rayNG.

The VLESS node times out and fails DNS resolution in Hiddify, resulting in the error message:

dns:exchange failed for https://example.org/ IN A:context canceled

Version

2.0.5 and 2.3.1

Platform/OS

Android

Additional Context

No response

Application Config Options

{
  "region": "cn",
  "block-ads": false,
  "use-xray-core-when-possible": false,
  "execute-config-as-is": false,
  "log-level": "warn",
  "resolve-destination": false,
  "ipv6-mode": "ipv4_only",
  "remote-dns-address": "udp://1.1.1.1",
  "remote-dns-domain-strategy": "",
  "direct-dns-address": "8.8.8.8",
  "direct-dns-domain-strategy": "",
  "mixed-port": 12334,
  "tproxy-port": 12335,
  "local-dns-port": 16450,
  "tun-implementation": "gvisor",
  "mtu": 9000,
  "strict-route": true,
  "connection-test-url": "http://cp.cloudflare.com",
  "url-test-interval": 600,
  "enable-clash-api": true,
  "clash-api-port": 16756,
  "enable-tun": true,
  "enable-tun-service": false,
  "set-system-proxy": false,
  "bypass-lan": false,
  "allow-connection-from-lan": false,
  "enable-fake-dns": false,
  "enable-dns-routing": true,
  "independent-dns-cache": true,
  "rules": [],
  "mux": {
    "enable": false,
    "padding": false,
    "max-streams": 8,
    "protocol": "h2mux"
  },
  "tls-tricks": {
    "enable-fragment": true,
    "fragment-size": "10-30",
    "fragment-sleep": "2-8",
    "mixed-sni-case": false,
    "enable-padding": false,
    "padding-size": "1-1500"
  },
  "warp": {
    "enable": false,
    "mode": "proxy_over_warp",
    "wireguard-config": "{\"private-key\":\"ANVlo8+zI44w18ZvXfNO8vYjv3W27qQWUMTy/GPb8U8=\",\"local-address-ipv4\":\"172.16.0.2\",\"local-address-ipv6\":\"2606:4700:110:8c86:ed7d:f6c0:fa07:d32a\",\"peer-public-key\":\"bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=\",\"client-id\":\"wmQ8\"}",
    "license-key": "",
    "account-id": "95969544-c07c-4e44-b979-d012b3d8f2a3",
    "access-token": "fbb23ef1-df62-4b4f-9e53-26e03190475d",
    "clean-ip": "auto",
    "clean-port": 0,
    "noise": "1-3",
    "noise-size": "10-30",
    "noise-delay": "10-30",
    "noise-mode": "m4"
  },
  "warp2": {
    "enable": false,
    "mode": "proxy_over_warp",
    "wireguard-config": "{\"private-key\":\"4E12GyCb+9f6TkkH0h9ApEUzFPi4XsxUIGQNruyalHI=\",\"local-address-ipv4\":\"172.16.0.2\",\"local-address-ipv6\":\"2606:4700:110:8a75:4bb7:8fb5:9243:d4af\",\"peer-public-key\":\"bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=\",\"client-id\":\"7WkE\"}",
    "license-key": "",
    "account-id": "6e4f4bd3-5c37-43a5-8664-d3effd6d81ea",
    "access-token": "8b6cac3a-96cd-4e89-ba2e-82bb192f683c",
    "clean-ip": "auto",
    "clean-port": 0,
    "noise": "1-3",
    "noise-size": "10-30",
    "noise-delay": "10-30",
    "noise-mode": "m4"
  }
}

Relevant log output

dns:exchange failed for https://example.org/ IN A:context canceled

Are you willing to submit a PR? If you know how to fix the bug.

titancomputer commented 4 hours ago

duplicate issue https://github.com/hiddify/hiddify-next/issues/1235