PuppyIP Resource Center
Network & Connection Troubleshooting 8 min Published 2026-11-17

SOCKS5 Works but HTTP Proxy Times Out in v2rayN TUN: Check routeOnly

SOCKS5 and HTTP CONNECT use different handshakes. Check routeOnly only when SOCKS works and HTTP keeps timing out in the same nested proxy.

Windows v2rayN TUN SOCKS5 HTTP CONNECT routeOnly

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • In a topology with nested proxies and TUN, a successful TCP or SOCKS request does not prove the HTTP CONNECT path works.
  • Test the local HTTP and SOCKS5 listeners against the same upstream, destination, and active core, and record real request results.
  • Only when SOCKS5 succeeds, HTTP CONNECT keeps timing out, and the active sniffing configuration matches should you back up and A/B test routeOnly. Restart fully before retesting.
  • If runtime sniffing.routeOnly is false, change only that value to true and fully restart under the same conditions. Attribute the result to this branch only if the protocol outcome changes with that variable.

Confirm that this is a protocol difference in a nested proxy

If Windows v2rayN TUN is active and the configuration uses a nested proxy, the same upstream SOCKS5 request may work while HTTP CONNECT times out. Compare the protocol entries first. HTTP CONNECT and SOCKS5 use different handshakes and destination handling; success in one protocol does not show that routing, sniffing, or forwarding behaves the same for the other.

Keep the upstream node, HTTPS destination, client TUN state, and network the same for both tests. Confirm that the request uses the client's nested rule. Do not substitute a successful result from another client or node for this protocol comparison.

Test local HTTP and SOCKS5 requests separately

Read the current HTTP and SOCKS listener ports from v2rayN, then request the same HTTPS target through each entry. The PowerShell commands below use Windows curl.exe and print only the HTTP status, not the response body. Results still describe only those real requests and should be interpreted alongside the client connection view and error category.

If the SOCKS request also fails, or the two tests use a different upstream, configuration, or destination, routeOnly is not yet an evidence-based next step. Confirm the local ports, active core, and proxy-chain settings first.

Compare local HTTP and SOCKS5 against the same target

powershell
$HTTP_PORT = 'REPLACE_WITH_CURRENT_HTTP_PORT'
$SOCKS_PORT = 'REPLACE_WITH_CURRENT_SOCKS_PORT'
curl.exe --silent --show-error --max-time 15 --proxy "http://127.0.0.1:$HTTP_PORT" --output NUL --write-out 'HTTP %{http_code}\n' https://www.cloudflare.com/cdn-cgi/trace
curl.exe --silent --show-error --max-time 15 --proxy "socks5h://127.0.0.1:$SOCKS_PORT" --output NUL --write-out 'HTTP %{http_code}\n' https://www.cloudflare.com/cdn-cgi/trace
Replace the values with the current v2rayN listener ports and run on the same PC with the same active configuration. These make real HTTPS requests; do not publish local ports or error output.

Check the active core and sniffing option

Confirm the current TUN core, nested upstream type, destination protocol, and relationship between v2rayN's saved and runtime configurations. Check whether routeOnly belongs to the sniffing setting actually applied to this request. A field with the same name in a configuration file does not prove that the active core loaded it.

routeOnly affects whether sniffed information is used for routing decisions. A mismatch can change destination or rule handling, so the setting is not a general “fix HTTP” switch. If SOCKS5 also fails, or it is unclear which core runs in TUN, stop and confirm the active configuration first.

A/B test routeOnly only when the symptoms match

Change routeOnly only when the same upstream SOCKS5 request succeeds, HTTP CONNECT keeps timing out, the TUN and nested proxy topology is confirmed, and runtime configuration shows sniffing enabled, destOverride containing http and tls, and routeOnly set to false. Record the original value, set only routeOnly to true, keep the upstream, authentication, node, port, and destination unchanged, then fully exit and restart v2rayN and the active core before retesting.

In this configuration branch, routeOnly=true uses sniffed information for routing decisions while preserving the original proxy destination; it is not an HTTP inbound switch. Sniffed domains may still affect route selection, so consider the impact first if the remote relies on the sniffed hostname to choose a route, and keep the original value for rollback.

Retest both protocols and the real page after restart

After restart, confirm the TUN core, runtime configuration, and routeOnly value. Then repeat HTTP and SOCKS5 requests with the same upstream, destination, and local ports. Once both real requests complete, load the destination page in the actual app. Panel latency, a passing configuration check, or a core shown as online does not replace a complete HTTPS request.

If HTTP CONNECT still times out, or changing routeOnly causes SOCKS5, other domain routing, or direct traffic to behave unexpectedly, restore the original value and continue diagnosis. Do not infer that every HTTP proxy, core, or node combination is fixed from one successful request.

Version and scope

This diagnostic branch applies to a nested proxy setup with Windows (system build 10.0.26200), v2rayN 7.23.4, sing-box TUN, and an Xray mixed inbound. For the same upstream and destination, it supports this specific configuration branch only when SOCKS5 succeeds but HTTP CONNECT times out with routeOnly=false, then both real requests complete after changing it to true and fully restarting.

A failure in PassWall device port forwarding or a source host's TCP connection has a different boundary. Check router ACLs and forwarding ranges or the source host's network path for those conditions.

Upstream issue #9921 describes a different topology for server-side domain routing: forcing routeOnly=true in v2rayN 7.24.5 broke that scenario, and the maintainer pointed to 7.24.6. It is not the same problem as this nested HTTP-proxy client A/B test and does not validate changing false to true here. Do not copy the setting across topologies.

Sources

Frequently Asked Questions

If SOCKS5 works, should HTTP proxy also work?

Not necessarily. They use different handshakes and destination handling. Make separate real requests to the same target.

Is routeOnly a general fix for HTTP timeouts?

No. Test it as a single variable only when SOCKS5 works, HTTP CONNECT fails in a nested TUN proxy, and sniffing applies to the request.

Can I judge the result immediately after saving the setting?

Fully restart the active core as required and confirm that the runtime configuration reloaded before retesting.

Does this guide apply to PassWall port ranges?

No. This guide covers nested proxy and sniffing behavior in Windows v2rayN TUN.