VPN Service mode does not work: connect: connection refused

[v1993]

Search first

• I searched and no similar issues were found

Platform/OS

Linux

OS version

CachyOS rolling

Hiddify Version

2.5.7

What Happened?

I am unable to get the VPN service working; the HiddifyCli tunnel run initializes the tunnel as expected but then keeps spamming errors (see log output section).

Minimal Reproducible Example (MRE)

1. Start HiddifyCli tunnel run in terminal (or enable the service)
2. Select "VPN Service" mode in the application
3. Try to connect
4. Check the HiddifyCli output

Expected Behavior

A connection is successfully established.

Additional Context

sudo netstat -lntup | grep 12334 provides no input, suggesting that the port is indeed not open. All other modes work, including VPN mode (as root).

Application Config Options

{
"region": "ru",
"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": "1.1.1.1",
"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": false,
"enable-tun-service": true,
"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": false,
"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",
"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",
"clean-ip": "auto",
"clean-port": 0,
"noise": "1-3",
"noise-size": "10-30",
"noise-delay": "10-30",
"noise-mode": "m4"
}
}

Relevant log output

INFO CORE STARTED:
Start Result: core_state:STARTED
ERROR[0000] [2734113132 6ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused
ERROR[0000] [2676090824 6ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused
ERROR[0000] [2952084197 17ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused
ERROR[0000] [217122754 17ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused
ERROR[0000] [1050311121 17ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused
ERROR[0000] [3035633687 2ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused
ERROR[0001] [764771159 1ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused
ERROR[0001] [2271578049 1ms] inbound/tun[tun-in]: dial tcp 127.0.0.1:12334: connect: connection refused

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

• I'm willing to submit a PR (Thank you!)

[github-actions]

With the release of v4.0.0 (pre-release), most reported issues have been fixed. We’re closing all current issues to start fresh.If you’re still experiencing the problem, please open a new issue and let us know.